lc_preview_add_group_member

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

With no annotations, the description fails to disclose behavioral traits. The term 'Preview' suggests no side effects, but this is not explicitly stated. The agent cannot confirm whether this is a safe, read-only operation.

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 single sentence is concise and front-loaded, but it is too minimal. While it avoids verbosity, it sacrifices necessary detail. It earns its place but could be improved with additional context without becoming lengthy.

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's complexity (3 parameters, no output schema, no annotations), the description is incomplete. It does not explain what 'preview' entails, what the return value is, or any constraints (e.g., required permissions). An agent would need to infer much from the tool name.

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%, and the description adds no meaning beyond the parameter names. The three parameters (email, group_id, token_ttl_seconds) are not explained; the description only mentions 'user' and 'group' implicitly.

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 action: 'Preview adding a user as a group member.' It specifies the resource (group) and the operation (preview add), distinguishing it from sibling tools like 'lc_preview_remove_group_member' and 'lc_add_group_member' (implied). However, it could more explicitly differentiate from similar preview actions.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives (e.g., actual add after preview), nor does it explain the purpose of previewing.

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