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

With no annotations, the description carries the full behavioral burden, and it does disclose one genuinely non-obvious trait: 'counts as a delivered solicitation the first time this account receives it,' which warns the agent about a metered side effect. It is silent on auth/permission needs, error behavior for a malformed or unknown id, and whether repeat fetches are free, so it is partial rather than complete.

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, front-loaded with the core action and key, with the payload list and billing caveat following. The field enumeration is dense and slightly crammed into the first sentence, but every clause carries information and nothing is padded.

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 single-parameter read tool with no output schema, the description usefully enumerates the returned contents, standing in for the missing return documentation, and flags the billing side effect. The remaining gap is the absence of any routing versus sibling tools, which a complex 13-tool surface would benefit from.

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 0%, so the description must compensate for the single nb_id parameter. It does identify the identifier domain ('NextBid id') and repeats the NB######## shape, but that format is already encoded in the schema pattern and the description does not say where an id comes from or what happens if it is unknown — partial compensation only.

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 names a specific verb and resource ('Full record for one opportunity') and pins the key ('NextBid id (NB########)'), then enumerates the payload (description, AI summary, buyer contacts, amendments, filed documents). That enumeration implicitly separates it from per-artifact siblings like list_documents and get_document_text, but it never explicitly states the relationship, so it stops short of a 5.

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?

There is no when-to-use or when-not-to-use guidance. The description never references search_opportunities (to find an id) or the document-level siblings (once you already have the record), and does not state prerequisites such as requiring a previously discovered NextBid id. The billing sentence is a cost note, not usage routing.

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