Api privacy personal data is sensitive retrieve

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

Annotations declare readOnlyHint=true and destructiveHint=false, but the description says personal data can be 'viewed or edited,' which implies a write capability. This directly contradicts the read-only annotation and makes the tool's behavior ambiguous.

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 boilerplate sentence, but it is generic and misleading rather than informative. Its brevity does not earn its place because it fails to state the actual retrieval purpose.

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 parameters and annotations covering safety, the description still fails to explain what 'is_sensitive' means or what the endpoint returns. It leaves the agent without enough context to know when this retrieval is useful.

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 tool has zero parameters, so there are no parameter semantics for the description to clarify. Schema coverage is 100% and the empty input schema is self-explanatory, making this a baseline 4.

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 says only that this is an 'API endpoint that allows personal data to be viewed or edited.' It does not mention the 'is_sensitive' retrieval aspect in the tool name, and it conflates viewing with editing. It also gives no clue how it differs from the many sibling privacy personal-data endpoints.

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?

There is no guidance on when to use this endpoint versus alternatives such as the personal data list, object retrieve, or update tools. The agent must infer usage entirely from the name and sibling list.

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