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

Annotations already declare openWorld, non-readOnly, non-idempotent behavior, so the description's value is the payment semantics it adds: the 402 challenge and the specific settlement rails returned. It stops short of describing failure modes beyond payment, side effects on the remote service, or whether executions are logged/repeatable.

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 sentences, front-loaded with the core capability and followed by the payment condition. The enumeration of four payment rails is dense but each names a real settlement path; nothing is padded.

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 universal dispatcher, the hardest thing an agent must know is the payment gate, and the description covers it precisely; return values are covered by the output schema and arguments by the schema field descriptions. Nothing essential to calling 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?

Schema coverage is 100% and the schema already enumerates accepted payment_proof formats and explains the arguments object. The description only adds the free-vs-paid gating context that determines whether payment_proof matters, so it earns the baseline 3 rather than more.

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?

States a specific verb and resource: execute any of the 121 Diogenes edge microservices. That is clearly distinct from the sibling verbs discover and inspect, although the description never explicitly says to resolve arguments via diogenes_inspect_tool first (only the schema's arguments field does).

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?

Gives the key routing rule: free-tier tools run with no payment, paid tools require payment_proof or return a 402 challenge. It does not spell out the prerequisite workflow (discover -> inspect -> execute) or when execution rather than inspection is the right choice; that is left to the sibling names and schema.

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