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

Annotations already disclose readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds modest behavioral context by stating the result is a 'complete current catalog,' implying no filtering or stale snapshot, but it does not discuss pagination, response size, or refreshes, so some behavioral ambiguity remains.

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, front-loaded sentence that states the action and object immediately, then lists the relevant output dimensions. Every listed field adds useful expectation-setting; there is no filler, repetition, or unnecessary context.

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, no-parameter, read-only catalog tool, the description is mostly complete: it enumerates the key return fields and indicates completeness and currency. However, there is no output schema to clarify return shape, and the description omits some details present in the schema description, such as access and runtime status, and gives no indication of pagination or result limits.

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 tool has zero parameters and the schema description covers the empty input object fully (100% coverage), so the description has no parameter burden to carry. The baseline for a zero-parameter tool is 4, and no additional parameter semantics are needed.

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 ('Return') and a clear resource ('the complete current catalog'), then itemizes the returned fields: service IDs, customer value, category, pricing, inputs, outputs, target networks, and payment behavior. This makes the tool's purpose unmistakable and clearly distinct from sibling tools like service_recommendation or verify_basic.

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 says what the tool does but gives no guidance on when to use it versus alternatives. It does not mention exclusions, such as 'use service_recommendation when you need a ranked recommendation' or 'use search/verify tools when looking up a single service.' The agent must infer the appropriate context from the sibling names.

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