client_deleteProfilePicture

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

There are no annotations, so the description carries the full burden of behavioral disclosure. The description only states the action but does not mention that deletion is permanent, whether it requires specific permissions, or any side effects across devices. 'Delete' implies destructiveness but does not add context beyond the name.

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, front-loaded sentence with no unnecessary words. It is concise and easy to parse. However, it may be too terse for a destructive operation, but that is more a completeness issue than a conciseness issue.

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 operation with one parameter and no output schema, the description tells what it does but lacks essential context about permanence, reversibility, and impact. Given that this is a deletion action, a more complete description would warn about irreversible changes or effects on the user's profile.

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 input schema covers the single parameter sessionId completely with type, example, and description. The description adds no additional parameter information. Since schema coverage is 100%, the baseline of 3 is appropriate; the description does not need to elaborate further.

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 action: 'Delete the current user's profile picture'. It uses a specific verb ('Delete') and resource ('profile picture') and distinguishes itself from sibling tools like client_setProfilePicture (sets a picture) and groupChat_deletePicture (deletes a group chat picture). The scope 'current user' is explicit.

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: use this when you want to remove the current user's profile picture. It does not explicitly state when not to use it or mention alternatives, but the purpose is self-evident and no competing tool for deleting a personal profile picture exists. No exclusions or context are provided, so the guidance is minimal.

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