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

Annotations already declare readOnlyHint=true; the description adds that it is a measurement record only, reinforcing the read-only nature and clarifying it is not a security audit. However, no additional behavioral details (e.g., rate limits, data freshness) are provided.

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?

The description is extremely concise, with only two sentences. The main action is front-loaded ('Look up the public Gold Rush Passport'), and the second sentence adds essential context without wasted words.

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?

There is no output schema, and the description does not describe the return value beyond calling it a 'measurement record'. The agent has no idea what fields or structure to expect, which is a significant gap for a lookup tool.

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 coverage is 0%, but the description indicates that the parameters are for an 'MCP URL or mcp_id', implying one of them is used. However, it does not specify format, constraints, or whether both can be provided, leaving ambiguity.

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 clearly states the tool's verb ('Look up'), resource ('public Gold Rush Passport'), and scope ('for an MCP URL or mcp_id'). It also clarifies it is for measurement, not security, which distinguishes it from sibling tools like provenance_verify_passport.

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?

The description provides some usage context ('Measurement record only, not a security audit') but does not explicitly state when to use this tool versus alternatives or what prerequisites exist. There is no mention of when not to use it.

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