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

With no annotations provided, the description carries the full burden. It discloses the return payload, cost in tokens, and the prerequisite of connected accounts. It does not explicitly mention irreversibility, but 'delete' implies destruction, so this is reasonable.

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 concise sentences: purpose, prerequisite, return value, and cost. It is front-loaded with the core action and includes no fluff, making it highly efficient.

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 presence of an output schema and clear prerequisite instructions, the description is fairly complete. It could mention potential errors or that the permission must already exist, but for a simple delete tool it covers the essential operational context.

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 coverage is 100% with descriptive parameter details, so the baseline is 3. The description adds little beyond repeating the clerk_instance_id guidance already present in the schema, such as 'Pass clerk_instance_id to target a specific connection.' It does not enrich parameter meaning meaningfully.

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 an organization permission from a connected Clerk application' with a specific verb and resource, clearly distinguishing it from sibling tools like delete_organization_role or delete_organization_membership. This is precise and unambiguous.

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?

It provides explicit usage context by instructing to call clerk.get_connected_accounts first and how to target a specific connection via clerk_instance_id. However, it does not explicitly differentiate from alternative delete tools or state when not to use it, though the purpose itself makes this clear.

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