lc_preview_delete_secret

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

No annotations are provided, so the description carries full burden. It says 'Preview deleting' but does not explain what the preview entails—whether it modifies state, checks permissions, returns a confirmation, etc. The behavioral traits are unclear.

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 very short (one phrase). While concise, it lacks necessary detail. It is not overly verbose but under-specifies, so it earns an average score.

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 absence of annotations, output schema, and parameter descriptions, the tool definition is incomplete. The description does not cover the context of what the preview outputs, error conditions, or prerequisites. More comprehensive information is needed.

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%, yet the description adds no information about the parameters. 'oid', 'name', and 'token_ttl_seconds' are left unexplained. The description does not help the agent understand which parameters are essential or how they relate to 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 action ('Preview deleting') and the target resource ('a secret Hive record'). This distinguishes it from sibling tools like 'lc_preview_delete_hive_record' (generic) and 'lc_get_secret' (read-only). The purpose is unambiguous.

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. For example, it does not mention that this is a dry-run simulation and that actual deletion should be performed by a different tool (e.g., lc_delete_secret).

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