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

Annotations only say readOnlyHint=false and openWorldHint=true, which are thin. The description adds meaningful behavior: per-call pricing in USDC on Base and a quote-before-payment flow. This is valuable context beyond the annotationshare. It does not disclose post-payment side effects or response behavior in detail, but what it adds is substantive and not contradictory.

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 tight sentences with no filler. The purpose is front-loaded, then pricing and quote behavior are added in the second sentence. Every clause 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?

Captures the essential payment flow and the generic nature of the tool, but lacks explicit guidance on where to resolve endpoint names (genesis402_catalog exists as a sibling) and on how the params object relates to the chosen endpoint. Given the high complexity of a 360-endpoint generic caller and no output schema, this is a notable gap.

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 description coverage is only 33%, so the description must compensate. It does clarify endpoint by saying 'by name' and payment_signature by explaining the quote-without-payment flow. However, the params object—which is the payload for actual endpoint execution—is left completely unexplained, and the free-form nature means the agent still has no direct guidance on how to structure it.

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: 'Calls any of the 360 Genesis402 endpoints by name.' The 'any' framing clearly identifies this as the generic dispatcher, and the category list (DeFi, SEC filings, research, etc.) reinforces that it covers the same domains as the dedicated siblings. It is easy to distinguish from the specific sibling tools like whois or token_brief.

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?

Implies usage: call this when you want to invoke a named Genesis402 endpoint. It gives price and quote behavior, which helps plan the call, but it never explicitly says to prefer dedicated siblings for known operations or to consult genesis402_catalog to discover endpoint names. No when-not-to-use guidance is provided.

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