lc_preview_set_user_role

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

The description implies a non-destructive action ('preview') but does not explicitly state that it is read-only or safe. With no annotations provided, the description should carry the burden of disclosure; it adds value by indicating the preview nature but lacks details on side effects or return behavior.

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, which is concise. However, it lacks necessary structural elements such as parameter explanations or usage context, making it minimally adequate. While not verbose, it sacrifices completeness for brevity.

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 tool has 4 parameters, no output schema, and no annotations, the description is insufficient. It does not explain the relationship between parameters, the nature of the preview result, or how to interpret the output. Critical context for safe and effective use is missing.

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 0%, yet the description adds no information about the four parameters (oid, email, role, token_ttl_seconds). It does not explain what 'oid' represents, valid formats for 'email', acceptable 'role' values, or the purpose of 'token_ttl_seconds'. The description fails to compensate for the missing schema descriptions.

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 tool's purpose: previewing a user's permissions replacement with a predefined role. It uses a specific verb ('preview') and identifies the resource (user permissions and role), which distinctively separates it from sibling tools like 'lc_preview_add_user_permission' or 'lc_preview_remove_user_permission'.

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. Among many sibling tools dealing with permissions and roles, there is no mention of appropriate contexts or exclusions, leaving the agent to infer usage without support.

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