deleteUserPhoto

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

Adds detail beyond destructiveHint annotation: states permanence, no soft-delete, and return value. Also advises user confirmation for bulk use.

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?

Well-structured with markdown headers, front-loaded, but slightly verbose. Every sentence adds value though.

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?

Fully covers purpose, parameters, behavior, return value, and alternatives. No output schema but return is described. Complete for a simple delete 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?

Single parameter photo_id is clearly explained as the record identifier. Though schema has no description, context makes it unambiguous.

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?

Clear verb and resource: 'Delete a user photo - Permanently delete a userphoto record by ID.' Distinguishes from siblings by mentioning updateUser alternative.

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?

Explicit 'Use when' section and 'See also' for alternatives like updateUserPhoto. Provides clear when-to-use and when-not-to-use guidance.

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