companies_delete_logo

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

No annotations are provided, so the description carries the behavioral disclosure burden. The description does add useful context about downstream effects ('PDFs will no longer include the company logo'). However, it doesn't disclose whether this is reversible, whether the logo file is permanently deleted, or any authorization/permissions needed.

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 tight two-sentence structure with zero waste. Both sentences earn their place — one states the core action, the other explains the practical downstream consequence. Appropriate length for a simple single-parameter tool.

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 tool with one required parameter, full schema coverage, and no output schema, the description is reasonably complete. The explanation of the PDF effect adds meaningful behavioral context. However, as a mutating/delete operation with no annotation coverage, some additional context around reversibility or permanence would strengthen completeness.

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?

Schema coverage is 100% with a single parameter (uuid, described as 'Company UUID'), so the schema fully documents the parameter. The description adds no further semantic detail about the uuid beyond what the schema provides, matching the baseline of 3 for high schema coverage.

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 tool removes a logo from a company ('Remove the logo from a company'). It uses a specific verb+resource structure consistent with the tool name. It doesn't explicitly distinguish from siblings, though the company_upload_logo sibling is the clear inverse counterpart, so context differentiates it.

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 indicates when to use it (to remove a company logo) but provides no explicit exclusions or alternative guidance. The immediate effect on PDFs is noted, which helps usage context, but there's no guidance on when NOT to use it or prerequisites.

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