assess_existing_infrastructure_tool

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety and side-effect profile. The description adds outcome context about identifying reuse and gaps, which aligns with the read-only behavior. It does not introduce any conflicting behavior and provides modest extra context beyond the annotations.

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 a single, focused sentence with no filler. It front-loads the core action and delivers the essential purpose efficiently. Every word contributes value, and no unnecessary information is present.

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?

The tool has two complex nested object parameters with no property descriptions, and the description does not clarify their structure or roles. Although an output schema exists, the input side is under-specified for an agent to invoke the tool correctly. The description explains what the tool does but not how to properly construct the required inputs.

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?

With 0% schema description coverage, the description carries the full burden of explaining parameters. It mentions 'declared infrastructure' and 'planning envelope' but fails to map these concepts to the actual parameters 'project' and 'existing_infrastructure'. An agent cannot determine which input is which or what fields are expected, making parameter usage ambiguous.

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 clearly states the tool's action: compare declared infrastructure with the planning envelope, and output reuse and gaps. It uses a specific verb and resource, making the tool's purpose unmistakable. However, it does not explicitly differentiate itself from sibling tools like analyze_inference_project_tool or recommend_architecture_tool, so sibling distinction is left to inference.

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 implies usage: this tool is intended for situations where there is declared infrastructure and a planning envelope to compare against. However, it provides no explicit when-to-use instructions, no exclusions, and no mention of alternatives among the sibling tools. The usage context is reasonable but not explicitly stated.

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