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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is covered. The description adds that it lists feeds and their availability, and points to the published OpenAPI spec, which is extra context beyond the annotations. No contradiction; it adds useful behavioral 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?

Two concise sentences with no filler. The first sentence states the core function and the second provides a helpful pointer to external documentation. The information is front-loaded and every word earns its place.

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 list tool with no parameters and no output schema, the description is complete: it states the resource, the type of information returned (feeds and availability), and a link to the OpenAPI spec for deeper details. An agent can call it confidently without additional context.

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 carries no parameter burden. The schema is empty and coverage is 100%, so there is nothing to explain. The baseline for 0 parameters is 4, and the description correctly focuses on what the tool returns rather than inputs.

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 states a clear action ('List') and a specific resource ('Namesake's free machine-readable feeds') and adds the detail that it shows their MCP/REST availability. This is distinct from the sibling tools (get_guide, get_name, list_guides, search_names) which are about names and guides, not feeds.

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 when to use it: whenever you need to discover available feeds and how to access them (MCP/REST). It does not explicitly name alternatives or exclusions, but the tool's purpose is self-evident and no sibling overlaps. It is clear enough without explicit when-not guidance.

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