squire

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

No annotations provided, so description carries full burden. Adds valuable context about 'fresh toolchain' isolation, but omits critical safety profile (read-only vs destructive/fixing), output format, or failure behavior. The word 'fixed' is ambiguous (pre-configured vs auto-fix).

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?

Single 19-word sentence with zero waste. Front-loaded with action verb, every clause earns its place explaining both what it does and why (environment drift prevention).

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?

For 5 parameters with full schema coverage, description adequately explains execution context (isolation) but lacks output behavior disclosure and safety profile given no annotations or output schema exist.

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 coverage is 100%, providing complete parameter documentation. Description does not add parameter-specific semantics (e.g., path formats, target globs) beyond what the schema already defines, earning baseline score.

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?

Specific verb 'Run' with clear resources 'lint and static-analysis tools'. The phrase 'fresh toolchain' effectively distinguishes from siblings like build, compile, test, and verify by emphasizing isolated environment execution.

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?

Implies clear usage context: use when you need to avoid 'local environment drift' affecting results. While it doesn't explicitly name alternatives, the value proposition (fresh toolchain vs local) guides selection. Lacks explicit prerequisites or 'when not to use' guidance.

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