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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context beyond that: newest-first ordering, default and maximum result counts, and the fields returned. It does not define the 'recent' time window or permission requirements, but it is substantially informative.

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 tight sentence that front-loads the action and resource. Every clause contributes scope, ordering, return fields, limits, or safety context without unnecessary preamble.

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 simple one-parameter list tool with no output schema, the description gives enough to call it correctly: ordering, result cap, returned fields, and read-only status. It could be slightly more complete by defining 'recent' or clarifying pagination beyond the 50-item cap.

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 carry parameter meaning. It adds the default of 10 and reinforces the maximum of 50, but the schema already states minimum 1 and maximum 50, and the description does not explicitly name or fully explain the limit parameter.

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 verb and resource: 'List the contractor's recent FieldDraft quotes.' It also specifies ordering and returned fields, making the purpose clear. However, it does not explicitly distinguish itself from siblings like get_quote or open_quotes.

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 does not explain when to use this tool instead of alternatives such as get_quote, open_quotes, or draft_quote. 'Recent' indicates scope but not selection criteria or exclusions.

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