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

Adds substantial context beyond the sparse annotations: fixed-fields-only input, no free text, the fact that reports aggregate into a public server rating and incident alerts seen by every agent, and 'No charge' cost disclosure. Annotation readOnlyHint=false correctly aligns with a write/submission operation, and the description explains its downstream effect well, though it does not cover repeat-submission or idempotency behavior.

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?

Front-loaded with the 'Use this after...' trigger and structured logically. It is a bit dense with several clauses, but each sentence (constraint, aggregate effect, alternative, cost) carries distinct information rather than 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?

For a 10-parameter telemetry submission tool with no output schema, the description covers the trigger, the input constraint, the consequence of reporting, and cost. Return-value behavior is not described, but the aggregate effect narrative largely compensates for a simple confirmation response.

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% and each of the 10 parameters is individually documented, so the schema does the heavy lifting. The description conceptually enumerates what to report (worked, why not, duration, match, surprises), which lightly reinforces the fields but adds no syntax or format 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 (report) and a well-scoped resource: the outcome of a call to an MCP server. The description immediately clarifies what is being reported (whether it worked, why not, duration, description match, surprises), so an agent can distinguish it from sibling tools 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?

Explicitly says when to use it (after calling a tool on an MCP server, especially one 7Maps pointed you to) and names an alternative mechanism (passing the same fields as last_trip on a paid call). It stops short of an explicit when-not-to-use, so it is strong but not exhaustive.

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