AroFlo MCP

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

Annotations declare readOnly/idempotent safety. The description adds valuable behavioral context: HTTP GET method, pipe-delimited query DSL syntax, mode options (data|verbose|debug|raw), and payload reduction via compact/select. It does not disclose rate limits, pagination cursor behavior, or the interaction between page/maxResults/maxItems limits.

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?

Dense, information-rich single paragraph. Front-loads the zone identification. Every sentence conveys specific syntax rules or configuration options. Slightly hindered by run-on structure with quoted examples mid-sentence, but efficient given the API complexity.

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 18 parameters and 0% schema coverage, the description covers the high-complexity query DSL adequately but neglects pagination parameter relationships. References external documentation appropriately for field validation. Output schema presence excuses lack of return value description.

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?

Critical gap: 0% schema description coverage across 18 parameters. The description partially compensates by documenting the complex query syntax (where/order/join), mode, compact, and select parameters. However, it fails to explain the pagination controls (page, pageSize, autoPaginate, maxPages, maxResults, maxItemsTotal, maxItems) and boolean flags (validateWhere, verbose, debug, raw), leaving significant semantic gaps.

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?

Specifies 'Query' (verb) and 'AroFlo TaskResources zone' (resource), distinguishing it from sibling task endpoints (taskmaterials, tasklabours). However, it does not clarify what constitutes a 'TaskResource' vs entities in those sibling zones, leaving domain ambiguity.

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 references external docs (aroflo://docs). However, it lacks explicit guidance on when to use this aggregate zone vs specific task endpoints (taskmaterials, tasklabours) and omits pagination strategy recommendations.

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