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

Annotations already provide destructiveHint=true and idempotentHint=true. The description adds key context: the entry is soft-deleted ('waits in the trash') and can be restored with its annotation. It also clarifies that tool events remain unchanged, which is beyond what annotations convey.

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 four sentences, each serving a purpose: action, usage constraint, soft-delete behavior, and side-effect clarification. It is front-loaded with the core action. Minor verbosity could be trimmed, but overall efficient.

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 single-parameter delete tool with no output schema, the description covers the essential behavioral aspects (soft delete, annotation removal, side effects on events). It does not specify return value or error handling, but the idempotentHint and destructiveHint provide safety. The description is sufficiently complete given the tool's simplicity.

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 100%, so baseline is 3. The description adds value by explaining how to obtain the entry_id ('call get_logbook to find it') and a constraint ('only manual entries carry an id'). This helps the agent correctly populate the parameter.

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: 'Take a manual logbook entry out of the logbook, and the annotation it placed on the curves with it.' It names the resource (manual logbook entry) and distinguishes from siblings like create_logbook_entry and restore_logbook_entry.

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?

The description explicitly says 'Only do it when the user asked for it: it is their logbook,' which guides appropriate use. It also mentions the alternative (restore_logbook_entry) and clarifies that tool events are unaffected, preventing misuse.

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