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

No annotations exist, so the description must carry the full burden. It mentions output content but does not disclose side effects, authentication requirements, rate limits, or whether the tool is read-only. This lacks sufficient detail for safe invocation.

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 sentence, efficiently conveying the core purpose and scope. Every word is necessary, and the 'FREE:' prefix provides a secondary context without redundancy.

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?

The description covers the output content but is vague on format (e.g., whether it returns a list or object). It does not mention prerequisites like authentication or existence of paid tools. Given no output schema, more detail on return structure would improve completeness.

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 input schema has no parameters, so the description cannot add parameter details. However, it effectively sets expectations by stating the tool returns pricing data for all paid tools, which is useful context for a parameterless tool.

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 clearly states the tool retrieves a price list, payment network, and PayTo address for all paid tools. It is distinct from sibling tools which focus on backtesting, bar quality, execution cost, and regime analysis.

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 implies usage when pricing information is needed but does not explicitly state when to use or avoid this tool, nor does it mention alternatives. The context of siblings suggests it is for pricing, but no direct guidelines are provided.

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