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. While 'Create' implies a write/mutation operation, the description doesn't address permissions required, whether entries are editable/deletable, rate limits, or what happens on success/failure. The existence of 'delete_logbook_entry' as a sibling suggests entries can be removed, but this isn't mentioned in the description.

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 with bullet-point Args is well-organized and front-loaded. However, the Args section could be more integrated with the description rather than appearing as a separate documentation block.

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 that an output schema exists (which should document return values), the description doesn't need to explain return values. However, for a 4-parameter mutation tool with no annotations and 0% schema description coverage, the description should provide more context about constraints, permissions, and error conditions. The basic parameter documentation is insufficient for full understanding.

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 Args section lists all 4 parameters with brief labels, but with 0% schema description coverage, this provides only basic semantic context. The description doesn't explain what constitutes valid project_id/logbook_id values, title/body_text constraints, or relationships between these parameters. It compensates minimally for the schema coverage gap.

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 ('Create a new entry') and resource ('in a logbook'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'create_logbook' or 'delete_logbook_entry', which would require more specific context about what distinguishes this particular creation operation.

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 provides no guidance on when to use this tool versus alternatives. There are many sibling creation tools (create_logbook, create_project, create_task, etc.), but no indication of what contexts or prerequisites make this tool appropriate. The Args section documents parameters but doesn't provide usage context.

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