strip_personal_info

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

No annotations are present, so the description must disclose behavior. It states it clears specific metadata fields and returns a success/error message, but it does not detail permanence, document state requirements, or whether track changes or other metadata are affected.

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 extremely concise with two sentences and a return line. It is front-loaded with the purpose and efficiently lists affected fields. No 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?

Given the tool has no parameters and no annotations, the description covers the basics (action, affected fields, return). However, it lacks information on prerequisites, reversibility, or comparison with siblings, which would be helpful for a complete understanding.

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 zero parameters and 100% schema coverage (empty), the description adds value by explaining what the tool does and what it modifies. The baseline for 0 params is 4; the description meets it by clarifying the action.

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 states the tool removes personal information from document metadata, specifically author, last modified by, and comments. It uses a specific verb and resource, distinguishing it from siblings like 'set_metadata' or 'redact_text'.

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 implies usage for privacy cleanup before sharing, but it does not explicitly state when to use it versus alternatives like manually editing metadata or using other sanitization tools. No when-not-to or alternative guidance is provided.

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