AroFlo MCP

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

Annotations declare safe read-only/idempotent behavior. Description adds valuable execution context: pipe-delimited clause syntax, payload reduction via compact/select, and mode variations (data/verbose/debug/raw). No contradictions with annotations.

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 but efficient. Front-loaded with purpose, followed by specific syntax examples for pipe-delimited clauses, then payload optimization hints. Every sentence provides actionable value, though the param overlap between mode enum and verbose/debug/raw booleans is left unexplained.

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?

Output schema is present so return values need not be described. However, given 19 parameters with zero schema coverage, the description should have addressed the pagination strategy (autoPaginate vs manual pages) and clarified the distinction between maxItems, maxResults, and maxItemsTotal. Sibling differentiation is also absent.

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 explaining complex WHERE/ORDER/JOIN pipe-delimited syntax, mode values, and compact/select usage. However, it fails to document 13 other parameters including pagination controls (autoPaginate, maxPages), result limits (maxItems/maxResults confusion), or the required 'zone' parameter's valid values.

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 specific verb 'Query' + resource 'AroFlo zone' with scope 'arbitrary'. Effectively distinguishes from sibling tools like aroflo_get_tasks which target specific entities.

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?

Implies flexibility via 'arbitrary zone' and references external docs, but lacks explicit guidance on when to choose this generic query tool versus the 40+ specific entity getters (e.g., 'use this when complex filtering across zones is needed, otherwise use specific getters').

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