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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds meaningful behavioral context beyond annotations: it tells the agent the operation is paginated and returns related evidence. It does not mention auth requirements or rate limits, but those are not critical missing details given the simple read-only nature.

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, well-structured sentence that front-loads the action and resource, then adds the key detail about paginated evidence. There is no fluff or redundancy; every word contributes. Despite not covering the parameters, conciseness is excellent because the content provided is efficient.

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 that there is no output schema and 0% schema description coverage, the description must explain the return structure and parameter usage. It does mention pagination and evidence, but it does not describe the shape of the response (e.g., whether the entity object is included, how evidence is structured, what the cursor refers to). The 'generation' parameter is entirely unexplained. For a tool with 4 parameters, the description is incomplete and leaves the agent with ambiguous instructions on how to call it effectively.

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 0% – the schema provides only property names, types, and constraints, with no semantic descriptions. The tool description does not compensate at all; it never mentions what 'id', 'limit', 'cursor', or 'generation' mean or how they affect the call. The agent is left to guess the purpose of these parameters, especially 'generation' which is not self-evident. This is a significant gap given the absence of schema descriptions.

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 states a specific verb ('Read') and resource ('verified organization or person, or a published topic'), and further clarifies the output ('with paginated related evidence'). This distinguishes it from siblings like search_evidence (which finds things) and get_evidence (likely for evidence directly). The scope is precise and immediately understandable.

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 clearly implies usage: when you have an ID of a verified org/person/published topic and want its details plus related evidence. It provides clear context but does not explicitly name alternatives or state when not to use this tool. However, the purpose is distinct enough that an agent can infer the appropriate situation, and no exclusions are needed.

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