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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description still adds real value by disclosing that the call is free and that the payload includes live prices, URL templates and a free sample (there is no output schema to convey this). Minor gap: no mention of pricing-refresh cadence or auth requirements on the host.

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?

One descriptive sentence followed by a two-clause usage directive; the enumeration is dense but each item adds routing information. Front-loaded with the resource being listed and zero filler.

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?

A no-parameter, read-only discovery tool with no output schema needs a description that says what comes back, and this one does (price, URL template, free sample). Combined with annotations covering the safety profile, an agent has everything required to call it correctly and act on the result.

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?

Zero parameters, so there is nothing to disambiguate; baseline applies. The description correctly implies a no-argument, host-wide listing.

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 ('List every paid API route on this Avasis host') and then enumerates the concrete route families covered (token safety verdicts, rug-check kits, Polymarket odds, page reader, chain tips, gas ops). It also names what each entry carries (price in USDC, URL template, free sample), so an agent knows exactly what this returns without opening the schema.

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?

'Free. Call it first, then avasis_quote for the route you want.' gives an explicit ordering rule and the next step, which is strong guidance. It does not say when to prefer avasis_free_sample or avasis_verdict_rubric instead, so sibling routing is only partially covered.

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