blast_radius

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

No annotations exist, so description must disclose behavior. It hints at 'mandatory completeness+staleness' and 'NO_SNAPSHOT' being an honest answer, but does not explain what these mean or whether the tool is read-only, destructive, etc. Lacks essential behavioral traits.

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?

Extremely terse (2 sentences), but sacrifices clarity. Important information about behavior and parameters is omitted. Not efficient; it's under-specified.

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 the complexity (10 params, nested objects, no schema descriptions, many siblings), the description fails to provide enough context for an agent to understand or use the tool correctly. Completely inadequate.

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 0% with 10 parameters including complex nested objects. The description provides no explanations for any parameters (e.g., repo, rev_range, changed_refs, filters). Adding zero value beyond the schema.

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 states it finds 'downstream affected entities from stored dated snapshots' but uses vague jargon like 'mandatory completeness+staleness' and 'NO_SNAPSHOT', making the purpose unclear. It does not effectively differentiate from siblings.

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?

No guidance on when to use this tool versus its many siblings (e.g., changed, heddle_impact_radius_get). No context about prerequisites or alternatives.

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