coda_delete_permission

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

The description discloses that revocation causes the principal to lose access unless other permissions exist, which is critical behavioral context beyond the annotations (destructiveHint=true). 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?

The description is four sentences, each carrying essential information: purpose, effect, nuance, and prerequisite. It is front-loaded and concise without unnecessary 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 the simplicity of the tool, the description covers the operation, its implications, and how to obtain the required input. With an output schema present, no further details on return values are needed.

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?

While the input schema already describes both parameters with 100% coverage, the description adds value by explaining that permission_id should come from coda_list_permissions, linking the tools together and providing cross-reference information.

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 uses the specific verb 'Remove' and resource 'permission entry' from a Coda doc, clearly distinguishing it from sibling tools like coda_add_permission and coda_list_permissions.

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 explicitly states when to use this tool (to revoke a permission), warns about potential access through other permissions, and instructs the agent to get the permission_id from coda_list_permissions first, providing clear guidance on prerequisites and alternatives.

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