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

The readOnlyHint annotation already establishes that this is a safe read operation, so the description adds value by disclosing the researcher-only access requirement and the explicit caveat that external identity ownership is not verified. This is meaningful behavioral context beyond the annotations, although response and error behavior are not described.

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 compact and every clause carries information: the resource, the restriction, and a key limitation. It reads as a fragment rather than a complete sentence, but for a simple single-parameter read tool the brevity is not excessive.

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?

With no output schema and no explanation of the 'id' parameter, the description does not provide enough for an agent to confidently call the tool. The researcher restriction and identity caveat add some context, but the input semantics and expected return data remain unspecified.

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 only parameter, 'id', has 0% schema description coverage and the description never mentions it. The schema provides only type and format, leaving the meaning of 'id' completely ambiguous. The description does nothing to compensate for this gap.

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 tool name supplies the verb ('read') and the description identifies a specific resource ('pseudonym mappings') and audience ('Researcher-only'). It is distinct from siblings like read_research_dashboard or read_research_export, though the description itself uses a noun phrase rather than explicitly stating that it returns mapping data.

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 when-to-use guidance or alternative routing is provided. The only usage-related information is the researcher-only restriction, which is an eligibility constraint rather than guidance on when to select this tool over a sibling. An agent would have to infer the appropriate context from the resource name.

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