lc_preview_delete_playbook

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

With no annotations, the description must convey behavioral traits. 'Preview' suggests no side effects, but this is not stated, nor does it mention idempotency, authentication needs, or output format. The description is insufficient for an agent to understand the tool's behavior beyond being a preview.

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 concise (5 words), but this brevity sacrifices clarity and completeness. It is front-loaded with the core action, but the lack of detail makes it less useful than a slightly longer description that adds critical context.

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?

For a tool with 3 parameters, no output schema, and 0% parameter description coverage, the description should compensate. It fails to explain the return value, parameter meanings, or when to use it among many similar preview delete tools. The description is completely inadequate for the context.

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 explanation for the three parameters (oid, name, token_ttl_seconds). The agent cannot infer what values to provide for 'oid' and 'name' (likely playbook identifiers) or how 'token_ttl_seconds' affects the operation.

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 verb 'preview deleting' and the resource 'a playbook Hive record'. It distinguishes from other preview delete tools by specifying the record type, and from non-preview tools by the 'preview' prefix. However, it does not explain what the preview entails (e.g., checks constraints or shows impact), leaving minor ambiguity.

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 guidance is provided. The description does not indicate when to use this tool rather than alternatives like lc_delete_playbook or other preview delete tools. The 'preview' prefix implies it's a safe check before deletion, but this is not explicit, and no alternatives or conditions are mentioned.

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