FleetQ

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

Annotations are empty, so the description carries full disclosure burden. It lists actions but doesn't explain side effects (e.g., what happens when rejecting, whether webhooks fire synchronously, idempotency, or permissions required). No behavioral traits beyond action names are disclosed.

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?

Compact single-sentence structure with parenthetical action summaries. Efficient length but the parameter name mismatches create noise. Front-loading of the noun phrase is appropriate.

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?

Insufficient for a 9-parameter polymorphic tool with complex conditional requirements (e.g., 'reason' only needed for reject, 'form_response' only for complete_human_task). Schema marks 4 fields globally required, which is misleading for actions like 'list', and description doesn't clarify action-specific parameter subsets.

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?

Despite 100% schema description coverage, the description introduces parameter name mismatches: it references 'comment' (schema: 'notes'), 'form_data' (schema: 'form_response'), and 'webhook_url' (schema: 'callback_url'). These inconsistencies could confuse the agent about actual parameter names.

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 'Manage approvals and human tasks' which identifies the domain, and enumerates specific actions (list, approve, reject, etc.) that clarify capabilities. However, 'manage' is a vague verb and the description doesn't distinguish this from sibling tools like workflow_manage or trigger_manage.

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 no guidance on when to use this tool versus the 20+ sibling '_manage' tools (e.g., workflow_manage vs approval_manage). No prerequisites, conditions, or exclusion criteria are mentioned.

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