permission-revokeRolePermission

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

No annotations provided. The description lacks any disclosure of behavioral traits such as side effects (e.g., immediate effect, cascading permissions), required permissions, rate limits, or error conditions. Agents have no information beyond the action itself.

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 extremely brief (one sentence plus tag). While concise, it omits critical context for a tool with three parameters, including a nested object. It is under-specified rather than efficiently concise.

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?

With three parameters, nested objects, and no output schema, the description is wholly inadequate. It does not explain the requestBody structure, the permission values, or how roles relate to workspaces. Sibling tools are similar, but no differentiation is provided.

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 description coverage is 33% (only requestBody has a generic description). The main description adds no parameter explanations. Agents must guess that workspacePublicId and rolePublicId are identifiers and that permission is an enum from the schema. No clarification of enum meanings or nesting.

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 clearly states the action 'Revoke a specific permission from a role' with a relevant tag. It distinguishes from sibling tools like permission-grantRolePermission and permission-revokePermission by specifying the target (role). However, it could be more explicit about the scope (e.g., workspace-level roles).

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 on when to use this tool vs. alternatives like permission-revokePermission (for members) or permission-grantRolePermission. The description does not mention prerequisites, ordering, or conflicts. Users must infer context from the tool name alone.

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