Delete Company Logo

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description reinforces that the action is permanent and cannot be undone, which adds minimal new behavioral context beyond 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 front-loaded with the key action, but it repeats 'This cannot be undone' and 'Permanently removes' unnecessarily. It is slightly verbose for a simple delete operation.

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 tool with one parameter and no output schema, the description covers the essential behavior and endpoint. However, the inconsistency between 'logo' and 'Company Settings' and the lack of return value information reduce 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?

The input schema documents company_id with a clear description. The description merely repeats that company_id is required, adding no additional meaning. Schema coverage is 100%, so baseline is 3.

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 states 'Delete company logo' and references the endpoint '/settings/logo', making the tool's purpose clear. However, it also says 'delete the specified Company Settings', which is slightly misleading as the tool specifically deletes the logo, not all settings.

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 provides a basic usage statement ('Use this to permanently delete...') but does not differentiate this tool from siblings like 'delete_the_project_logo' or other delete tools. No guidance on when to use vs alternatives is given.

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