lc_preview_add_user_permission

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

Description mentions 'preview' implying no actual side effect, but does not explicitly state that it is safe or read-only. With no annotations, the description fails to disclose behavioral traits like whether it modifies state or requires specific permissions.

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 but lacks structure. It could benefit from being slightly more detailed without becoming verbose.

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 4 parameters, no output schema, and no annotations, the description fails to provide adequate context. It does not explain the return value, any prerequisites, or side effects, leaving the agent with insufficient information to use the tool correctly.

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 has 4 parameters (oid, email, permission, token_ttl_seconds) with 0% schema description coverage. The tool description does not explain what these parameters represent or how they should be used, leaving the agent without critical semantic context.

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?

Description clearly states the action: 'Preview granting one permission to a user.' It uses a specific verb and resource, and the naming convention differentiates it from sibling tools like 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 on when to use this tool vs alternatives (e.g., lc_preview_set_user_role, lc_preview_invite_user). The description lacks context about prerequisites or appropriate conditions for previewing a permission grant.

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