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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. Beyond that, the description usefully discloses the returned content set (route, stamps, signatures, comments, badges) in the absence of an output schema, though it says nothing about behavior for an unseen visitor_name or about result volume.

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?

A single front-loaded sentence with a colon-delimited enumeration that puts the resource before its contents. No filler, no redundancy.

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 one-parameter, read-only, closed-world tool with no output schema, listing what the passport contains is the key missing piece and it is supplied. Remaining gaps are minor: no note on unknown names or on how much history is returned.

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 the schema itself explains the 40-char limit, the stable-identity property of the name, and why reads need no name. The description only restates "under this visitor_name" and adds no format or semantics beyond the schema, so baseline 3 applies.

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?

The description pairs a specific verb ("Show") with a concrete resource ("passport") and enumerates its contents: route, stamps, signatures, comments, badges. That is far clearer than the bare name/title, though it never distinguishes itself from adjacent personal-status tools such as get_postcard, my_messages, or todays_hunt.

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?

Usage is only implied: "earned so far under this visitor_name" suggests a personal progress summary, but there is no explicit when-to-use statement, no exclusion, and no pointer to sibling tools that surface overlapping data (get_postcard, my_messages). The agent must infer the routing.

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