Delete A Company Office

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

Annotations already mark destructiveHint and idempotentHint; description adds context that deletion is permanent, cannot be undone, and a repeat call returns 404. Also discloses error payload format and common HTTP statuses, which goes beyond the annotations. No contradiction with 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?

Description is well-structured with action first, then prerequisites, permanence, errors, and endpoint. However, it repeats the id resolution instruction twice ('Confirm the target id' and 'resolve it with the matching list tool'), and includes API endpoint and path that may be unnecessary for an agent. Still, each section is relevant and readable.

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?

Covers prerequisites, permanence, repeat-call behavior, failure modes, required parameters, and API context. For a simple delete tool with 2 params and no output schema, this is comprehensive. No major 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?

Schema already covers both parameters with descriptions (100% coverage). Description adds guidance that id must identify an existing parent record and should be resolved via the list tool, adding practical semantics beyond the schema. The 'Required parameters' repetition adds little, but the resolution guidance is valuable.

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?

States clearly 'Deletes an Office associated to a Company' with a specific verb and resource. Distinguishes from related office tools (list/show/update) through the destructive action. Also clarifies permanent removal.

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?

Explicitly instructs to confirm the target id with the matching show/list tool before calling and to resolve id with the matching list tool. Provides error status guidance (401/403/404), implying when the call will succeed. Does not explicitly contrast with update_company_office, but the delete context is clear.

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