lc_preview_remove_user_permission

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

With no annotations, the description carries the full burden but only states 'Preview revoking one permission.' It does not disclose what happens after the preview (e.g., need to confirm), any side effects, or authentication requirements. The behavioral implications are unclear.

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 a single sentence that is front-loaded with the action. It is concise, but this conciseness sacrifices completeness. The structure is minimal yet 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 complexity (4 parameters, no output schema, no annotations), the description is severely incomplete. It fails to explain the preview workflow, parameter purposes, or return value. For a tool with many siblings, more context is 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?

Schema description coverage is 0%, so the description must compensate. It fails to explain any of the 4 parameters (oid, email, permission, token_ttl_seconds). The phrase 'one permission from a user' vaguely maps to email and permission but adds no detail about the parameters' roles or formats.

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 'Preview revoking one permission from a user' is specific with a verb and resource, and distinguishes from sibling tools like lc_preview_add_user_permission and lc_list_user_permissions. However, it does not clarify what 'preview' entails, leaving some ambiguity.

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 such as lc_preview_add_user_permission, lc_list_user_permissions, or lc_explain_permission. The description lacks context on when to preview a removal vs. actually removing or listing permissions.

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