Binalyze AIR MCP Server

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

With no annotations provided, the description carries full burden but only states the initiation action. It doesn't disclose whether this is asynchronous, where results are delivered, what format the export uses, permissions required, rate limits, or whether it's a one-time or recurring operation. For a tool that presumably creates data exports, this is insufficient behavioral disclosure.

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 a single, efficient sentence that communicates the core purpose without any wasted words. It's appropriately sized for a tool with one parameter and gets straight to the point.

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?

For a tool that initiates data exports with no output schema and no annotations, the description is inadequate. It doesn't explain what happens after initiation, where to find results, what format they're in, or any error conditions. Given the complexity of export operations and lack of structured information, more context is needed.

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 schema description coverage is 100%, so the schema already documents the single parameter completely. The description doesn't add any parameter information beyond what's in the schema, which is acceptable given the high schema coverage, resulting in the baseline score of 3.

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 ('Initiate an export') and resource ('audit logs from the AIR system'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list_audit_logs' or 'export_case_activities', which would be needed for a perfect score.

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 like 'list_audit_logs' or other export tools. It doesn't mention prerequisites, timing considerations, or what makes this tool distinct from similar operations.

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