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

The annotation readOnlyHint=true already communicates the read-only safety profile. The description adds one behavioral nuance ('Unknown independence never counts as independent endorsement'), which is useful, but it does not disclose other behavioral aspects such as failure behavior, accessibility of data, or whether the reputation is computed on demand.

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 two short sentences with no filler. The main purpose is front-loaded, and the second sentence adds a meaningful interpretive rule without 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?

The tool has no output schema, 0% schema coverage, and 3 parameters, yet the description provides only a one-line purpose and a semantic rule. It omits the return shape, parameter details, error conditions, and additional context needed for an agent to confidently invoke the tool 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?

With 0% schema description coverage, the description must compensate for missing parameter meaning. It clarifies that 'id' is a subject or agent UUID and hints at 'kind', but it does not explain the valid values for 'kind', the meaning/usage of 'context', or how these parameters interact, leaving significant 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 states a specific verb ('Read') and resource ('diagnostic public reputation') for subject or agent UUIDs, making the tool's purpose immediately clear. It does not explicitly compare against sibling tools, but 'reputation' is unique enough among the listed siblings to avoid confusion.

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 phrase 'Read diagnostic public reputation' implies the tool should be used when a subject/agent's public reputation is needed. However, it gives no explicit guidance on when not to use it or when to choose an alternative tool such as read_trust or read_subject, leaving the selection decision partly to inference.

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