download-template

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses that the tool downloads to a temporary directory and requires a follow-up copy command, which adds useful behavioral context. However, it lacks details on permissions, error handling, or what happens if the template already exists, leaving gaps for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with critical information ('CRITICAL: MANDATORY FIRST STEP') and uses two concise sentences that earn their place by stating the action, context, and required follow-up. There is no wasted text, making it highly efficient and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and 2 parameters with full schema coverage, the description is mostly complete. It covers purpose, usage, and behavioral steps, but as a mutation tool (download implies write operation), it could benefit from more details on side effects or error scenarios. The lack of output schema is mitigated by the clear post-action instructions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both parameters. The description does not add specific parameter details beyond the schema, but it implicitly reinforces the importance of 'frame' by mentioning 'pre-configured starter template' and 'InsForge projects,' aligning with the schema's framework focus. Baseline is 3, but the contextual reinforcement slightly enhances understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the tool's purpose: 'Download pre-configured starter template to a temporary directory.' It specifies the action (download), resource (starter template), and context (InsForge projects). It clearly distinguishes this from sibling tools like 'create-bucket' or 'run-raw-sql' by focusing on project initialization.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidelines: 'CRITICAL: MANDATORY FIRST STEP for all new InsForge projects' indicates when to use it, and 'After download, you MUST copy files to current directory using the provided command' specifies post-action requirements. It implies alternatives are not applicable for this initial step, offering clear context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.