Aedifion MCP Server

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

No annotations are provided, so the description carries full burden. It implies a read operation ('Get') but doesn't disclose behavioral traits like whether it returns all logbooks at once or paginates, what happens if the project_id is invalid, or if authentication/permissions are required. This leaves significant gaps for a tool that likely interacts with project data.

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 appropriately sized and front-loaded with the core purpose in the first sentence. The Args section is clear but could be integrated more seamlessly. There's no wasted text, though it could be slightly more polished in structure.

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 tool's low complexity (1 parameter) and the presence of an output schema (which handles return values), the description is somewhat complete but lacks behavioral context. Without annotations, it should ideally mention more about usage constraints or error cases to fully guide an agent, but the output schema reduces the burden.

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 adds minimal semantics: it clarifies that 'project_id' is 'The project's numeric ID', which is slightly more informative than the schema's 'Project Id' title. However, with 0% schema description coverage and only 1 parameter, this doesn't fully compensate for the lack of schema details, but it meets the baseline for minimal parameter info.

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 verb 'Get' and resource 'all logbooks in a project', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_logbook' (singular) or 'create_logbook', leaving room for ambiguity about when to use this versus those alternatives.

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 like 'get_logbook' (singular) or 'create_logbook'. The description only states what it does, not when it's appropriate or what prerequisites might exist (e.g., needing a valid project_id).

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