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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds meaningful context: the tool returns filtered line items, costs $0.02 USDC per call, is cryptographically attested, and provides a verification URL. No contradiction with annotations. It omits auth/rate-limit details, but these are secondary given the read-only safety profile.

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 front-loaded with the use case and return type, and the example is illustrative. But the example contains a stray 'w.' and the description mixes core functionality with payment and attestation details in a way that adds slight noise. It is compact but not tightly polished.

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?

For a 7-parameter tool with no output schema, the description gives enough to attempt a call: use case, filters, example output counts, and cost. However, it leaves unclear what 'limit' controls, what fields each bid tabulation line item contains, and whether any filter combination is required. The absence of an output schema makes these gaps more significant.

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 57%, and the description names the main filter dimensions: owner, county, district, state, and letting date range. This adds meaning to county and district, which lack schema descriptions. However, it does not explain the limit parameter, the exact format beyond what the schema says, or how filters combine. It partially compensates but does not fully cover the gap.

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 a specific operation: returning construction letting bid tabulation line items filtered by geography and letting date range. This distinguishes it from the generic benchmark/synthesis siblings, though it does not explicitly differentiate it from get_intel_findings_search or get_intel_unit_prices.

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 opens with an explicit 'Use when scoping upcoming or recent construction lettings...' and provides a concrete example scenario. However, it does not mention when not to use this tool or name an alternative, so it falls short of a 5.

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