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

With no annotations, the description carries the burden of behavioral disclosure. It reveals important constraints: 'Returns up to 10 pages per request' and 'URLs must be from docs.redpanda.com/api/doc/*.' It also sets expectations for the response content without describing error handling or authentication, which prevents a 5.

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 three short paragraphs, each earning its place: the first states purpose, the second gives the usage workflow, and the third lists operational constraints. It is front-loaded with the key verb and resource, with no filler.

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 two-parameter retrieval tool without an output schema or annotations, the description is nearly complete. It explains what is returned, how to use it, and key constraints. It lacks only edge-case behavior like error handling or rate limits, but the core selection and invocation information is present.

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 already covers both parameters thoroughly, including the 'context' parameter rules. The description adds value by specifying the URL domain restriction and reiterating the 10-page limit, which goes beyond the schema's description for 'urls'.

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 opens with 'Retrieve full content of API reference pages by URL' and clearly specifies the return value: 'complete endpoint details including parameters, request/response schemas, and examples.' It distinguishes itself from sibling tools by explaining it consumes URLs from list_api_reference_pages or search_api_reference.

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 provides clear workflow guidance: 'Use this after finding pages via list_api_reference_pages or search_api_reference. Pass the URLs from those results directly.' It names the relevant sibling tools and implies the intended sequence, though it does not explicitly state when not to use the tool.

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