lc_preview_add_group_org

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

No annotations provided, and description fails to disclose any behavioral traits. It does not state whether the preview is read-only, what it validates, or if it has side effects. For a 'preview' operation, this is a critical gap.

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?

Single sentence is concise, but under-specification means it does not earn its place. Better to expand with key details than remain brief but uninformative.

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 no output schema, no parameter descriptions, and no behavioral info, the description is completely inadequate. The agent cannot understand what the preview returns, how to interpret results, or whether it is safe to call.

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%, and description does not explain any parameters. Parameter names (group_id, member_oid, token_ttl_seconds) provide some semantic hints, but 'member_oid' is ambiguous (likely organization OID) and 'token_ttl_seconds' is unexplained. No additional meaning beyond names.

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 'Preview adding an organization to a group', specifying the verb (preview adding) and resource (organization to a group). Distinguishes from siblings like lc_preview_add_group_member by focusing on organization. However, it does not explain what 'preview' entails.

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. No mention of prerequisites, when not to use, or related tools like lc_confirm_action. Usage is only implied by the action name.

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