Aedifion MCP Server

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

No annotations provided, so description carries full disclosure burden. While 'Get' implies read-only safety, the description lacks details on error behavior (task not found), what specific details are returned, or side effects. Minimal behavioral context given.

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?

Front-loaded action statement is efficient. The Args section uses standard docstring format which is appropriate given the schema's 0% description coverage, though it adds minimal new information. No verbose redundancy.

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 output schema exists (per context signals), return value description is unnecessary. For a simple single-parameter getter, the description is minimally adequate but misses error condition documentation and relationship to sibling list operations.

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 0%, requiring description compensation. The Args section provides minimal semantic value by labeling the parameter as 'The task ID', confirming integer usage. However, it omits format constraints, valid ranges, or provenance (where to obtain valid task IDs). Just meets minimum threshold.

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?

Clear verb 'Get' and resource 'details of a task' establishes the read operation. However, it fails to differentiate from sibling 'get_project_tasks' (which retrieves multiple tasks), risking incorrect selection when the agent needs to fetch tasks by project versus fetching a specific task by ID.

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 provided on when to use this single-task retrieval versus 'get_project_tasks' for listing. No prerequisites mentioned (e.g., that the task_id typically comes from a previous project tasks query).

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