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

With no annotations provided, the description carries the full disclosure burden, and it does reveal meaningful traits beyond the schema: evidence-linked determinations, deterministic identity, duplicate-suppression idempotency, and a mutation gate. Yet 'mutation gate' is never explained, and the side-effect profile is unclear (e.g., what resolve_address triggers or whether the tool persists anything), so the behavioral picture remains incomplete.

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?

Four short sentences with the usage context front-loaded and zero filler; every sentence earns its place. The output list, however, is dense jargon ('deterministic identity, duplicate-suppression idempotency, mutation gate') that slightly hampers readability, keeping it from a perfect 5.

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?

An output schema exists and the complex inputs are largely self-documenting, so the lack of return-format detail is not a liability. But for a tool with this much surface area, there is no routing guidance between single vs. batch variants, no mention of when projectpermit_info is the right call, and no disclosure of resolve_address side effects — leaving an agent to guess at the edges.

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 description coverage is high (83%), which sets a baseline of 3, and the description adds genuine parameter-level guidance: family+action as the mandatory starting point, a known-facts-only policy to avoid guessing, and the role of context.prior_decision_identity for repeat checks. That is real value beyond the per-field schema text.

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 identifies a specific purpose — evaluating proposed work before quoting/scheduling — and names the resource (project requirements) with an inventory of what it returns. It is clear about the tool's job, but it never differentiates itself from the sibling check_project_requirements_batch or projectpermit_info, so it falls short of a 5 on the sibling-distinction bar.

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?

It explicitly scopes when to use the tool ('Use for proposed work before quoting/scheduling') and gives entry guidance ('Start project with family + action and add only known facts'), plus a concrete repeat-check instruction via context.prior_decision_identity. However, it names no alternatives or when-not-to-use exclusions, leaving the choice versus the batch sibling implicit.

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