squire

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

No annotations provided, so description bears full disclosure burden. Adds useful context about 'clean toolchains' (isolated environments) and 'checks' (verification purpose), but omits critical behavioral details like whether outputs are preserved, if the operation modifies source directories, or specific toolchain side effects.

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 dense sentence that front-loads the action ('Run...'). Every clause earns its place: 'target-specific' modifies the action, 'clean toolchains' describes the environment, and the negative constraint efficiently differentiates scope without wasted words.

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?

Adequate for a 4-parameter tool with complete schema documentation and simple types. However, given the lack of annotations and output schema, gaps remain in behavioral disclosure regarding output handling and side effects that would be necessary for an agent to fully trust the operation.

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?

Input schema has 100% description coverage, establishing a baseline score of 3. The description mentions 'target-specific' and 'Go or Rust' which align with the 'targets' and 'language' parameters, but does not add substantial semantic detail, validation rules, or format syntax beyond what the schema already documents.

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?

Uses specific verb phrase 'Run...compilation checks' and identifies specific resources 'Go or Rust'. Explicitly distinguishes from the sibling 'build' tool via the scope constraint 'without turning Squire into a full CI or release system', clarifying this is for verification, not artifact generation.

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?

Provides clear scope boundaries by stating what the tool is NOT for (full CI/release system), which implicitly guards against inappropriate use for release builds. However, lacks explicit naming of the 'build' sibling as the alternative for those use cases.

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