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

Annotations already mark this as read-only and non-destructive, so the description does not need to restate that. It adds useful context by describing feeds as 'free machine-readable' and providing an OpenAPI link, which helps the agent understand the nature and discoverability of the output. The bar is lower due to strong annotations, and the description adds appropriate value.

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 consists of two concise sentences that front-load the core purpose ('List Get2Great's free machine-readable feeds') and then provide a valuable OpenAPI link. There is no redundant or filler content; every part 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?

Given the tool has no parameters, read-only annotations, an output schema, and a link to the full OpenAPI specification, the description is complete. The agent has everything it needs to select and invoke the tool correctly without additional elaboration.

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 zero parameters, so the baseline is 4. The description correctly avoids inventing parameter details and simply describes the operation. There is no parameter ambiguity to resolve, and the schema fully covers the empty parameter set.

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 the specific verb 'List' and the resource 'Get2Great's free machine-readable feeds,' which clearly identifies the tool's function. The resource is distinct from the sibling tools that focus on magazine articles and management tools, so the agent can easily differentiate it.

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 this tool should be used when the agent needs to list Get2Great's free machine-readable feeds, which gives some context. However, it does not explicitly mention when not to use it or compare it to the sibling tools, leaving the usage guidance implied rather than explicit.

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