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

readOnlyHint=true already covers the safety profile, and the description goes beyond that by disclosing that the payload contains PII and that responses are JSON:API { data } shaped, plus the underlying REST path. It omits permission requirements and rate-limit behavior, but for a read-only getter this is solid added context.

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?

One dense sentence that leads with the action and resource, then layers in the result type, the PII caveat, and the REST mapping. No filler, and the most important information is front-loaded.

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, the description does the work of describing the return shape (JSON:API data envelope) and its sensitivity (PII), which is exactly what an agent needs. Auth requirements and error conditions remain unstated, a minor gap for a simple read tool.

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 coverage is 100% for the single report_id parameter, and the description's 'report_...' hint merely echoes the schema's own example. No additional meaning about id provenance or format is provided, so the schema baseline of 3 applies.

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 ('Get'), the resource ('a single report by id'), and even defines what a report is ('screening/monitoring result, e.g. watchlist, adverse-media, business lookup'). It implies the single-vs-list split with persona_list_reports but never names that sibling, so it stops 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?

Usage is only implied: it presupposes the caller already has a report_id. There is no explicit when-to-use/when-not guidance and no reference to persona_list_reports as the way to discover ids, leaving the agent to infer the routing.

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