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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered (and 'Read-only' merely echoes it). The description adds genuine value the annotations don't: it discloses the payload contents, including quota_remaining broken out for geocoding, routing, and isochrone requests, plus seat plan values and key expiry.

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 dense but well-ordered sentences: identity and payload first, usage note last. Every clause maps to real returned data, though the parenthetical seat/quota enumeration makes the second sentence slightly heavy.

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 an output schema present the return shape needn't be re-explained, yet the description still names the key result fields, tells the agent when to call it, and repeats the read-only nature. Nothing needed to invoke a zero-parameter, read-only guidance tool is missing.

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?

The tool takes zero parameters, so there is nothing for the schema to document and the baseline of 4 applies. The description correctly adds no parameter discussion, consistent with an empty arguments object.

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 (Returns) and resource (the EZT MCP operating guide), then enumerates exactly what that covers: cross-tool workflow order, shared rules, result.server_version, and seat/quota details. An agent can tell this is a meta/onboarding tool distinct from task-oriented siblings like workflow_advisor or analyze.

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?

'Useful at the start of a session or for a host that does not show server instructions' gives explicit when-to-use context. It does not, however, name or exclude any alternative sibling (e.g., workflow_advisor), so the routing guidance is context without explicit alternatives.

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