deleteUserPhoto

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

The description adds significant behavioral context beyond annotations: 'Permanently delete... cannot be undone via API', 'No soft-delete via API', and includes return format. It complements the destructiveHint and idempotentHint annotations without contradiction.

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 concise and front-loaded with the most critical information (destructive nature, permanent deletion). Every sentence adds value without unnecessary verbosity.

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?

For a simple delete-by-ID tool with no output schema, the description covers all necessary aspects: purpose, usage context, alternatives, behavioral implications, and return value. Annotations handle safety flags, and sibling differentiation is addressed.

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 compensates by stating 'Required: photo_id' and implying it is the ID of the photo. While minimal, it adds meaning beyond the bare schema. Baseline for zero params is 4, and this tool has one param, so a 4 is appropriate.

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 'Delete a user photo - Permanently delete a userphoto record by ID.' It uses a specific verb and resource and explicitly differentiates from related tools like updateUserPhoto and updateUser with image actions.

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 provides explicit usage guidance: 'Use when: removing a photo attachment.' It also gives clear alternatives for member image management and advises confirming intent with the user before bulk use due to destructive nature.

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