Aedifion MCP Server

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

No annotations provided, so description carries full burden. Mentions BACnet priority range (1-16) which constrains behavior, but lacks disclosure of mutation semantics (overwrites existing?), idempotency, side effects on physical devices, or error handling. 'Write' implies mutation but safety characteristics unspecified.

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?

Standard Python docstring format with purpose front-loaded in first sentence followed by Args block. Appropriately sized given the need to document four parameters with no schema support. No unnecessary fluff, though 'The' prefixes in Args could be removed for tighter prose.

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?

Input parameters documented sufficiently given schema gaps, and presence of output schema (per context signals) excuses lack of return value description. However, for a BACnet control operation, lacks operational context (protocol handshaking, persistence guarantees, priority arbitration behavior) that would aid agent decision-making.

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?

With 0% schema description coverage, the Args section successfully documents all 4 parameters. Particularly adds value for 'priority' (BACnet protocol constraint 1-16) and 'project_id' (numeric constraint). 'Datapoint identifier' is redundant with schema title but acceptable given mandatory compensation for zero schema coverage.

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 'Write' with specific resource 'setpoint value' and target 'datapoint'. Distinguishes from sibling operations like 'delete_setpoint' and 'get_setpoint_status' through the write/read/delete distinction, though could clarify what distinguishes a setpoint from other writable values (e.g., timeseries).

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?

Provides no guidance on when to use this versus 'write_project_timeseries' or other write operations. Does not explain when to use specific priority levels (1-16) or when null priority is appropriate. No prerequisites or error conditions mentioned.

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