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

The readOnlyHint annotation already signals safety, and the description adds useful behavioral context: 'Public scores and safety findings are never altered' reinforces immutability, while 'fixed histories' implies append-only or unchanging records. This goes beyond simply restating read-only intent.

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 short, front-loaded with the primary purpose, and every sentence adds some meaning. It is not padded, though a brief parameter hint would make it even more useful without hurting conciseness.

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 simple one-parameter read tool, the description is too thin to be fully actionable: the critical meaning of 'id' is omitted, and with no output schema, the agent does not know what the response will contain. The read-only guarantee is helpful but does not compensate for the missing parameter semantics.

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 one required parameter, 'id,' with a UUID format but no description, and the schema description coverage is 0%. The tool description never mentions what 'id' refers to—whether it is a presentation ID, a research subject ID, or something else. The agent has no way to know how to populate this parameter correctly.

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 identifies a read operation on a specific resource: 'your consented reputation presentation and fixed histories.' This is more specific than a bare tool name, but it does not distinguish from closely related siblings like read_reputation, read_research_dashboard, or read_research_export, so it falls short of full differentiation.

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 gives no explicit guidance on when to use this tool rather than alternative read tools. It implies some consent-related context with 'consented,' but it never states the conditions that select this tool over read_reputation or read_research_dashboard, nor does it mention any exclusions.

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