lc_preview_delete_job

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

The description implies a preview (non-destructive) operation but does not explain what the preview returns (e.g., a token, summary), whether it requires special permissions, or any side effects. Without annotations, the description lacks necessary behavioral details.

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 too sparse for a tool with three parameters and no schema coverage. It sacrifices essential detail for brevity.

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 number of parameters, lack of annotations, and presence of many sibling preview tools, the description is grossly incomplete. It does not cover prerequisites, return values, or the overall workflow.

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?

The description does not explain any of the three parameters. The schema has no descriptions, so the agent is left without context on what 'oid', 'job_id', and 'token_ttl_seconds' represent.

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 states the verb 'preview deleting' and the resource 'service job record', which is specific. However, it does not differentiate this from other preview delete tools in the sibling list, lacking explicit context about what makes this tool unique.

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. It does not mention that it is a dry-run before confirming deletion, nor does it indicate any prerequisites or associated confirmation steps.

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