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

Annotations already mark it read-only and non-destructive, but the description adds useful behavioral context: it does not charge a payment method and some product classes remain unavailable unless separately released.

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?

Three short sentences, front-loaded with purpose, followed by prerequisite and constraints. No sentence is redundant or padding.

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 quote tool with no output schema, the description covers purpose, prerequisite, availability constraints, and the no-charge behavior. Only minor details such as quote expiry or link lifetime are omitted.

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 coverage is 0%, so the description must carry parameter meaning. It does so by explaining that product_id must be exact and come from gisdb_search_catalog, though the schema pattern itself documents the required format.

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?

States a specific verb and resource: get the buyer checkout link and fixed price for an available records product. It is meaningfully distinct from sibling tools such as gisdb_create_checkout and gisdb_search_catalog.

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?

Gives an important prerequisite (exact product_id from gisdb_search_catalog) and an exclusion (CAD/statewide packages unavailable), but does not explicitly say when to use this quote versus gisdb_create_checkout.

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