nlm_delete

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

Discloses permanent deletion and conditionality on confirm, but lacks details on auth needs, side effects (e.g., cascade to artifacts), recovery options, or latency. With no annotations, the description should provide richer behavioral context.

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?

Extremely concise single sentence with no redundancy. While efficient, it may be too terse—adding a second sentence could improve clarity without being wordy.

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?

Despite having an output schema (not shown), the description omits return value details, prerequisites, and edge cases (e.g., what happens if notebook doesn't exist). Given tool complexity (2 params, no annotations), more completeness 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%, and description only adds meaning to confirm (must be true). The 'notebook' parameter remains unspecified (e.g., expected format, required scope). Does not compensate for missing schema descriptions.

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 the action (permanently delete) and resource (notebook) with a condition (confirm must be true). However, it does not differentiate from sibling tools like nlm_download (which might also modify state) or provide context about what 'delete' means relative to other tools.

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 explicit guidance on when to use this tool vs alternatives. The description implies a prerequisite (confirm true) but does not mention when deletion is appropriate, reversible alternatives, or consequences of misuse.

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