lc_preview_remove_user

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

No annotations are provided, so the description carries full burden. It states 'preview removing' but does not clarify that this is a dry-run with no actual changes, nor does it mention required permissions, rate limits, or what the output represents.

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 short but lacks essential details. It is concise in length but underspecified, making it insufficient for an agent to understand the tool fully. Every sentence should earn its place; here it does not provide enough value.

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 (3 parameters, no output schema, no annotations), the description is severely incomplete. It does not mention what the preview returns, the effect of token_ttl_seconds, or any prerequisites. The tool likely requires specific permissions, but that is absent.

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 description does not explain any of the three parameters (oid, email, token_ttl_seconds). With 0% schema description coverage, the description fails to add meaning beyond the parameter names. For example, 'token_ttl_seconds' is not described.

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 ('preview removing a user from an org') which matches the tool name. It is specific about the verb and resource. However, it does not differentiate from sibling preview tools like lc_preview_remove_group_member, which also involve removal.

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. The description implies its use case but does not give context or exclusions, such as needing to use lc_preview_remove_user_permission for removing permissions instead.

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