removeBusinessAccountProfilePhoto

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

No annotations exist, so the description carries the behavioral disclosure burden. It does disclose the required bot right and the success return value. However, it does not describe failure behavior, reversibility, or the broader effect of removing a public vs. private photo, which the parameter schema partially covers.

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?

Two sentences with no filler. The core action, target, required permission, and return value are all stated efficiently and in order of relevance.

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 mutation tool, the description plus fully documented schema covers the essential invocation details: what to act on, the required right, and the success return. Minor gaps remain around edge cases and failure modes, but they are not critical for an agent to call the tool correctly.

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?

Input schema coverage is 100%, and both parameters have meaningful descriptions in the schema. The tool description adds no additional parameter-level detail beyond what is already structured, so the baseline score of 3 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 uses a specific verb ('removes') with a specific resource ('current profile photo of a managed business account'). This clearly distinguishes it from sibling setBusinessAccountProfilePhoto and other photo-related tools.

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 when to use it: whenever the agent needs to remove a business account profile photo. It also states the required permission, which is useful. However, it does not explicitly mention alternatives or exclusions, such as 'for setting a photo, use setBusinessAccountProfilePhoto'.

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