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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, repeatable read. The description's auth note ('no auth needed for public listings') adds genuine context beyond the annotations, but nothing is said about result scope, pagination, or rate limits.

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 short, front-loaded sentences with no filler, and the purpose precedes the access caveat. The terseness is efficient but borders on under-specification given the tool's 11-parameter surface.

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 an 11-parameter, no-output-schema search tool with low schema coverage, the description is far too thin: it explains neither filtering/pagination semantics nor anything about result shape, defaults, or the country field's worldwide caveat. An agent could call it, but largely by guessing at parameter behavior.

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 18% across 11 parameters, so the description is expected to compensate and does not: it mentions no parameters at all. Fields like limit/offset, remote, min_amount/max_amount, and tag have no schema description and no description-level explanation, leaving their semantics (pagination vs. filtering) ambiguous.

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+resource ('Find open offers and requests') that an agent can distinguish from the singular get_listing and the write-side create_listing. It does not explicitly name a sibling alternative, but the search-vs-fetch distinction is inferable from the wording.

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?

'No auth needed for public listings' gives one useful access condition, implying the tool can be called freely by unauthenticated clients. However, it never says when to use this search versus get_listing, my_listings, or list_categories, so routing is left to inference.

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