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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds valuable context: the tool is free, lists 52 endpoints, and covers specific categories (trading intelligence, AI inference, etc.). The verb 'List' implies a read-only operation, so no side effects are expected, though it does not explicitly state the absence of side effects or describe the return format in detail.

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 two sentences, front-loaded with the core function ('List the full AI Rook endpoint catalog with prices'). The parenthetical enumeration of endpoint categories is efficient and adds useful detail without bloat. No wasted words.

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 zero-parameter listing tool with no output schema, the description is nearly complete: it states what the tool returns (the catalog with prices), the cost (free), and when to use it (start here). It could optionally mention whether the result is paginated or the exact structure of the catalog, but given the simplicity of the tool, the description is sufficient.

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, so the description does not need to explain parameter meanings. The baseline of 4 applies because the schema is trivially complete (empty object) and there is nothing to add.

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 action ('List') and the resource ('full AI Rook endpoint catalog with prices'), including the endpoint count and categories. It distinguishes itself from sibling tools like call_paid_endpoint and get_quote, which perform specific actions rather than listing the 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?

The description explicitly instructs users to 'START HERE before calling any paid endpoint', providing strong when-to-use guidance. It also mentions the tool is free, reinforcing it as a safe, initial discovery step. This is sufficient context to guide tool selection among the siblings.

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