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

No annotations are provided, so the description must fully disclose behavioral traits. However, it does not mention whether the tool is read-only, what it returns, or any side effects. The description is misleading as it suggests a verification process rather than a data retrieval function.

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 a single sentence but it is not concise for a tool description: it reads like a tutorial on how to perform verification rather than a compact summary of the tool's functionality. It is verbose and poorly structured.

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?

Given no parameters, no output schema, no annotations, and 9 sibling tools, the description fails to explain what the tool does, what it returns, or how to use it. An agent would be unable to determine the tool's purpose or invoke it correctly.

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 input schema has zero parameters, so schema description coverage is 100%. There is no need for parameter information in the description, and a baseline of 4 is appropriate.

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 talks about 'how to verify a GSC surface's residency claim' which is instructional rather than stating what the tool does. It does not clearly indicate that the tool returns a residency receipt, and it fails to distinguish from sibling tools like get_fleet or resolve_carrier.

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?

No guidance is provided on when to use this tool versus alternatives. The description is a how-to guide, not a usage guideline, and does not mention any context or prerequisites.

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