Aedifion MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a write operation, implying mutation, but doesn't address critical aspects like required permissions, whether it overwrites or appends data, rate limits, error handling, or what the output schema contains. This leaves significant gaps for an agent to understand the tool's behavior.

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 well-structured and efficient, with a clear purpose statement followed by parameter explanations. Both sentences add value without redundancy. It could be slightly more front-loaded by integrating the parameter details into the main flow, but overall it's concise and readable.

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 complexity (a write operation with structured JSON input), the description covers the basics but lacks depth. It explains parameters and the action, but with no annotations and an unspecified output schema (though one exists), it misses behavioral context like side effects, error cases, or output format. For a mutation tool, this is minimally adequate but leaves room for improvement.

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 includes an 'Args' section that explains both parameters: 'project_id' as a numeric ID and 'timeseries_data' as a JSON string with a specific structure. However, with 0% schema description coverage, the schema provides no additional details. The description compensates adequately by defining parameter purposes and the JSON format, but doesn't clarify constraints like valid value ranges or time formats.

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 ('Write timeseries data') and target resource ('to datapoints in a project'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'write_setpoint' or 'delete_project_timeseries', which handle similar data operations but on different resources.

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. It doesn't mention prerequisites (e.g., needing an existing project or datapoint), nor does it contrast with sibling tools like 'get_project_timeseries' (for reading) or 'delete_project_timeseries' (for removal).

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