Aedifion MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a deletion operation but provides no information about permissions required, whether deletion is permanent/reversible, what happens to associated data, or any rate limits. For a destructive operation with zero annotation coverage, this is a significant gap in behavioral transparency.

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 efficiently structured with a clear purpose statement followed by parameter documentation. The two-sentence format is appropriately concise, though the parameter documentation could be slightly more informative given the 0% schema coverage.

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 destructive operation with 2 parameters and no annotations, the description provides basic purpose and parameter information. The existence of an output schema means return values don't need explanation in the description. However, given the tool's destructive nature and lack of behavioral annotations, the description should provide more guidance about consequences and prerequisites to be truly complete.

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%, so the schema provides no parameter documentation. The description adds basic parameter names and their purpose ('project_id: The project's numeric ID', 'logbook_id: The logbook ID'), which provides essential semantic information. However, it doesn't explain format constraints, valid ranges, or relationships between parameters beyond what's implied by their names.

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 ('Delete') and resource ('a logbook'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'delete_logbook_entry' or 'delete_project', but the verb+resource combination is specific enough for basic understanding.

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 about when to use this tool versus alternatives like 'delete_logbook_entry' or 'delete_project', nor about prerequisites or consequences. The description only restates what's obvious from the tool name without contextual usage information.

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