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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description does not need to restate safety. It adds meaningful behavioral context by indicating pagination ('bounded page') and an authentication requirement ('authenticated organization'), which are not in the annotations.

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?

A single sentence that is front-loaded and contains no filler. Every phrase contributes meaning: 'bounded page' signals pagination, 'safe' aligns with read-only behavior, 'product catalog metadata' identifies the resource, and 'authenticated organization' scopes the operation.

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 paginated read-only listing tool, the description plus the rich annotations, input schema, and output schema provide everything an agent needs. Return values are covered by the output schema, and safe behavior is covered by annotations, so the description is complete enough.

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?

The schema covers businessId and cursor with descriptions, leaving limit only structurally defined. The description adds some meaning by hinting at pagination ('bounded page') and organization scoping, but it does not explicitly explain how limit and cursor relate to the listing behavior, so it only partially compensates for the schema's 67% coverage.

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 uses a specific verb ('List') and resource ('product catalog metadata'), and adds scope ('for the authenticated organization'). It clearly distinguishes this from sibling tools like list_businesses and get_subscription by naming the exact resource being listed.

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 gives useful context ('bounded page', 'safe product catalog metadata', 'authenticated organization') but does not explicitly state when to use this tool versus alternatives such as list_businesses or get_receivables_summary. Usage is implied rather than made explicit.

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