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

With no annotations provided, the description is the sole source of behavioral disclosure. It states the tool returns a manifest, is free, and lists the manifest's contents, implying a read-only scope with no side effects. It doesn't specify the exact output format or potential size limits, but for a discovery tool with zero parameters, this is adequate and does not contradict any annotations (since there are none).

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 short paragraphs with the core action front-loaded, followed by a clear 'When to use' line and a cost note. Every sentence earns its place: purpose, usage guidance, and cost. No redundancy or fluff.

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's simplicity (no parameters, no output schema), the description fully covers what it does, what the manifest includes, when to use it, and that it's free. The 'machine-readable manifest' phrasing hints at the output format, and the enumerated contents compensate for the absence of an output schema. Nothing an agent needs to call it correctly is missing.

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 appropriately adds no parameter information. The empty schema already indicates this, and the description doesn't need to explain missing fields. The baseline of 4 for zero parameters is justified because the description complements the schema without redundancy.

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 specific verb ('Return') and a precise resource ('the full machine-readable manifest of Vortex'), enumerating exactly what the manifest contains (operations, prices, input schemas, payment). This clearly distinguishes it from sibling tools, which are individual operations like credit_deposit or find, by positioning it as the whole-API discovery tool.

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?

It explicitly provides a usage condition: 'Call this first if you have never used Vortex and want to know what it can do and what it costs.' This gives clear when-to-use context, and the sibling tools are the alternatives one would use after this discovery call, so the guidance is effectively unambiguous.

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