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

No annotations are provided, so the description carries the burden. It discloses that the tool is free and provides a flat list of all tools/endpoints with their metadata. The verb 'list' clearly implies a read-only operation, and the inclusion of 'every' indicates exhaustive enumeration. It doesn't mention auth requirements, rate limits, or response size, but for a simple catalog with zero parameters, these are minor gaps.

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, front-loaded sentence that starts with the key 'Free:' modifier and immediately states the action ('list') and the resource. It contains no filler and every word contributes to the tool's purpose.

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, read-only listing tool with no output schema, the description fully specifies the contents of the returned list: each tool/endpoint with its price, params, and a sample HTTP URL. This is sufficient for an agent to understand what the tool returns and when to call it.

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 and the schema is empty. The description's statement 'every data tool/endpoint' explicitly communicates that no filtering is needed or provided, which fully justifies the absence of parameters and adds meaning beyond the empty schema.

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 uses the specific verb 'list' with a clear resource 'every data tool/endpoint' and enumerates the included attributes (price, params, HTTP sample URL). This clearly distinguishes the tool from sibling data-query tools, as it's a metadata/discovery tool rather than a data source.

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 implicitly indicates usage: it's a free, comprehensive listing of all available tools and their metadata, so an agent would use it to discover endpoints or pricing. However, it does not explicitly state when not to use it or name alternatives, though the siblings are obviously the specific data tools themselves.

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