squire

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

No annotations provided, so description carries full burden. Adds 'clean environment' execution context and crucial service availability status (rejects jobs) that is not in the schema. Does not describe output format or 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?

Two sentences with zero waste. First establishes purpose, second states critical operational limitation. No redundant information. Front-loaded with the core validation purpose.

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?

Appropriate for 4-parameter tool with full schema coverage. Mentions key service limitation and execution environment ('clean'). Missing output description but no output schema exists to require it. No annotations to supplement.

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% (file, language, targets, timeout all documented). Description adds context that the file is a 'dependency manifest' but does not elaborate on parameter interactions or syntax beyond what the schema provides. Baseline 3 appropriate.

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?

Clear specific verb 'Validate' with resource 'dependency manifests' and scope 'clean environment'. Identifies the domain (dependencies) which distinguishes from siblings like 'build' or 'test', though could explicitly differentiate from 'verify'.

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 critical limitation that 'public zero-egress service currently rejects deps jobs', which functions as a when-not-to-use warning. However, lacks explicit guidance on when to choose this over siblings like 'verify', 'build', or 'test' for validation tasks.

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