AroFlo MCP

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

Annotations already declare readOnly/idempotent status. Description adds valuable behavioral context: query DSL syntax (pipe-delimited), default mode value (data), payload reduction behavior (compact/select), and references documentation resource for schema discovery. 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?

Information-dense single paragraph packs essential DSL syntax, default values, and documentation pointers with minimal redundancy. Every phrase earns its place, though line breaks would improve readability for the multiple distinct concepts covered.

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 a complex query tool with 18 parameters and output schema. Successfully explains non-obvious query syntax and points to external documentation for dynamic field values. Missing explicit pagination behavior description, but schema structure implies standard pagination.

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 query parameters (where, order, join syntax) and control options (mode, compact, select), but leaves 12+ parameters undocumented (pagination flags, boolean switches like autoPaginate/validateWhere, and the relationship between mode enum and verbose/debug/raw booleans).

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 specific verb (Query) + resource (AroFlo Timesheets zone) and HTTP method (GET). Clearly distinguishes from 40+ sibling get_* tools by naming the specific zone/resource (Timesheets) in the first sentence.

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 clauses, ORDER format, and JOIN areas, plus mode options. Lacks explicit 'when not to use' or sibling comparisons, but the specific resource name provides clear contextual boundaries.

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