clio_delete_grant

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

The description mentions routing and scope (JWT, tenant, company) but does not disclose any behavioral traits such as destructiveness, required permissions, or side effects. Since no annotations are provided, this is a significant gap for 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 short but includes routing details that may be unnecessary for an AI agent. It front-loads the operation name but does not waste words.

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 is a delete tool with a single parameter and an output schema (unseen), the description is incomplete. It fails to explain what arguments are needed, what a successful deletion looks like, or error conditions.

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 only parameter 'arguments' is described as 'JSON string of arguments for the connector operation' with no specification of what keys are required (e.g., grant ID). With 0% schema description coverage, the description adds minimal value beyond the schema itself.

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 identifies the tool as 'delete_grant' but does not explicitly state that it deletes a grant. The purpose is implied by the name but not clarified, leaving ambiguity about what a 'grant' is in the Clio context.

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?

No guidance is provided on when to use this tool versus alternatives like clio_create_grant, clio_get_grant, clio_update_grant, or clio_list_grants. The description gives no context for selection.

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