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

Annotations already indicate destructiveness (destructiveHint: true). The description adds valuable context beyond that: removing the logo triggers fallback to agency branding. This adds concrete behavioral expectation without contradicting the annotations.

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 one tightly packed sentence that conveys the action, the target, and the behavioral consequence. No filler words; the most important information is front-loaded.

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 one-parameter destructive action with an output schema and annotation coverage, the description covers purpose and consequence. It could explicitly mention irreversibility or alternatives, but the destructive hint and sibling list already provide much of that context.

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 single parameter id is fully described in the schema as 'Client ID (from list_clients)', achieving 100% coverage. The description does not add meaning beyond what the schema already provides for this parameter, so the baseline of 3 applies.

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), the resource (client's full logo/logo_url), and the specific scope (client rather than account). This distinguishes it from siblings like remove_account_logo and remove_client_favicon.

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 gives clear context: use it to remove a client's full logo, with the consequence that agency branding takes over. It does not explicitly name alternatives or state when not to use it, but the client-specific language makes the intended scenario clear.

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