AroFlo MCP

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

Annotations establish read-only/idempotent safety. The description adds substantial behavioral context: specific pipe-delimited query syntax ('and|field|=|value'), response modes (data/verbose/debug/raw), and payload reduction controls (compact/select). It does not contradict annotations and effectively explains the non-standard query DSL beyond the schema structure.

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 efficiently packed into a single dense sentence with a documentation reference. Every clause provides unique value: HTTP method, query syntax, data types, mode options, and optimization hints. No redundancy, though the density impacts readability slightly.

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 complex parameters with zero schema descriptions, the description covers the essential query DSL but leaves critical gaps—particularly regarding pagination strategy (when to use autoPaginate vs manual page/maxItems) and the 'extra' parameter's purpose. The output schema existence excuses return value documentation, but input governance remains under-specified for a tool of this complexity.

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, the description carries significant load but delivers incomplete compensation. It thoroughly documents the complex query parameters (where, order, join) with syntax examples, and explains mode/compact/select. However, it completely omits pagination semantics (page, autoPaginate, maxPages, maxResults) and the purpose of boolean flags (verbose, debug, raw) versus the mode enum.

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 identifies the action 'Query' and specific resource 'AroFlo TaskMaterials zone', distinguishing it from sibling task-related zones (taskexpenses, tasklabours, tasks). However, it assumes domain knowledge of what a 'zone' represents in AroFlo, slightly tempering absolute clarity.

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?

Usage is implied by the specific resource name (TaskMaterials), but the description provides no explicit guidance on when to choose this over siblings like aroflo_get_tasks or aroflo_get_inventory. It does reference external documentation for valid fields, which aids discovery.

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