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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description only needs to add what they don't. Disclosing 'Costs $0.002 via x402' is genuinely valuable, non-obvious context an agent needs before calling, and the enumerated report scope clarifies the operation's depth. No auth or rate-limit details, but for a read-only report that is a minor gap.

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?

Three short, front-loaded sentences with zero filler: scope first, input source second, cost last. Every sentence carries information the agent needs and none repeats structured fields verbatim.

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?

With no output schema, the description usefully compensates by enumerating what the report returns (uptime, latency, price history, security findings), and the cost line covers a decision-critical factor. Only the routing question against sibling report/status tools is left unaddressed.

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 100% with a single parameter already documented as 'Service id (slug) from search results', so the baseline is 3. The description restates that source and adds a small extension ('or recommend results'), but provides no format or validation detail beyond the schema.

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 ('Full vetting report for one service') and enumerates the report contents (uptime, latency, price history, security findings), which separates it from the narrower get_service and get_service_status. It never names those siblings explicitly, so the differentiation is inferential rather than stated.

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?

'Takes an id from search or recommend results' tells the agent where the required argument comes from, which is real usage guidance. However, it never says when to pick this over get_service, get_service_status, or preflight_check, and gives no exclusions or prerequisites beyond the id source.

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