AroFlo MCP

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

Annotations already declare readOnly/idempotent safety. Description adds valuable domain-specific context: pipe-delimited query syntax, JOIN area examples, mode options, payload reduction via 'compact'/'select', and critical reference to 'aroflo://docs/api/<slug>' for field validation given openWorldHint=true.

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?

Information-dense single paragraph with no filler. Front-loaded with HTTP method and resource. Syntax examples are concrete. Slightly dense; could benefit from logical separation between query syntax and response formatting options.

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?

Appropriate for complexity: references external documentation for open-world schema discovery, explains payload optimization for potentially large datasets, and relies on existing output schema. Missing only pagination behavior details which would complete the picture given the parameter richness.

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 has 0% description coverage. Description compensates by detailing complex query parameters (where/order/join syntax, mode values, select format), but omits semantics for 11 parameters including pagination controls (page, autoPaginate, maxPages) and boolean flags (verbose, debug, validateWhere).

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?

States 'Query the AroFlo WorkOrders zone (GET)' with specific verb and resource. Clear it retrieves workorders specifically, though it does not explicitly differentiate from siblings like 'aroflo_get_tasks' or 'aroflo_get_workorderlineitems' which appear related.

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 detailed syntax guidance for pipe-delimited WHERE/ORDER clauses and JOIN areas, plus references documentation resources. However, lacks explicit guidance on when to select this tool versus sibling getters like 'aroflo_get_tasks' or the generic 'aroflo_query_zone'.

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