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

The description warns about altering production data, which is good. However, it does not clarify that deletion is permanent or destructive, and the annotation 'destructiveHint: false' contradicts the implied destructive nature of a delete operation.

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 relatively concise and includes a useful production warning, but the structure is somewhat jumbled, mixing general write operations with delete-specific details and referencing undefined parameters.

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?

Given that this tool is for delete operations, the description lacks specific context such as how to target a single record vs bulk delete, expected outcomes, and prerequisites. It does not adequately distinguish this tool from its write siblings, leaving the context incomplete.

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 description introduces an 'action' parameter not defined in the input schema. It explains id and parent_id requirements but does not clearly describe the use of 'ids' for bulk operations or how 'body' is used in delete, leaving parameter semantics incomplete.

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 'cria/atualiza/remove' (create/update/remove) which implies all write operations, but the tool name is specifically for delete. This ambiguity makes it unclear that the tool is exclusively for deletion of Ordem de Serviço records.

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 mentions requirements like needing an id for update/patch/delete and parent_id for nested resources, but does not explicitly say when to use this tool versus the create/update/patch siblings. It also references an 'action' parameter that is not present in the schema, adding confusion.

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