remove_business_account_profile_photo

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

The description says 'remove' which implies a destructive action, but the annotation destructiveHint=false. This is a direct contradiction; removing a profile photo is inherently destructive (replaces/removes existing data). No other behavioral context is provided beyond the annotation, and the description adds no clarity about permissions, reversibility, or effects.

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, direct sentence with no filler. It is appropriately front-loaded with the action, but it is so brief that it misses opportunities to add value. Still, for what it includes, it is concise and well-structured.

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?

The description lacks critical context: no explanation of return values (no output schema), no mention of photo_id optionality, no guidance on prerequisites, and no clarity on the distinction between business and personal profile photos. With minimal annotations and no parameter descriptions, the agent is left with significant gaps.

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 lists business_connection_id (required) and photo_id (optional), but the description does not explain their purpose or semantics. With 0% schema description coverage, the agent has no information about what these parameters mean, how to obtain them, or how they influence the removal operation.

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 (remove) and resource (business account profile photo), making it easy to distinguish from related tools like remove_my_profile_photo or set_business_account_profile_photo. It could be more explicit about the business-account scope vs. personal, but the verb+resource is specific enough.

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?

No guidance on when to use this tool versus alternatives such as remove_my_profile_photo (for personal accounts) or set_business_account_profile_photo (for setting/updating). The description does not mention any prerequisites or context, leaving the agent to infer usage from the name.

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