AroFlo MCP

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

Annotations declare read-only/idempotent safety; description adds valuable behavioral context including the GET method, pipe-delimited query syntax ('and|field|=|value'), mode options (data|verbose|debug|raw), and payload reduction controls (compact/select), plus documentation resource references.

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 paragraph with zero filler; front-loaded with primary action, though the single-block format packs many syntax rules together which could benefit from structural breaks for readability.

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 high complexity (18 params, custom query DSL) and 0% schema coverage, description adequately covers the domain-specific query language but has clear gaps in pagination/utility parameters; output schema exists so return values don't need description coverage.

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, description partially compensates by detailing syntax for critical params (where, order, join, mode, compact, select) including format examples, but leaves 12 parameters (pagination controls like autoPaginate, maxPages, maxItems) completely undocumented.

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?

Description opens with specific verb+resource ('Query the AroFlo Quotes zone') and HTTP method ('GET'), clearly distinguishing this from 40+ siblings like aroflo_get_quotelineitems or aroflo_get_tasks by specifying the exact zone being accessed.

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 usage context through 'Quotes zone' and mentions JOIN areas like 'lineitems' (hinting at relationship to sibling aroflo_get_quotelineitems), but lacks explicit when-to-use guidance versus alternatives or prerequisites like API authentication.

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