superpos_poll_tasks

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

Discloses empty return behavior and filtering. No annotations provided, so description carries full burden; it covers key aspects but omits potential side effects or read-only nature.

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?

Two efficient sentences, front-loaded with purpose, no redundant words.

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?

Adequate for a poll tool with output schema. Covers filtering and empty return, but lacks details on ordering or polling behavior, though not critical.

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?

Only explains 'capability' parameter. With 0% schema coverage, description fails to explain 'limit' and 'hive_id', leaving ambiguity.

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 clearly the verb 'list' and resource 'pending tasks' with added context about filtering and empty return. Distinguishes from sibling tools like get_task and claim_task.

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 for finding work to claim, and when to filter by capability. Lacks explicit when-not-to-use or alternatives but is clear enough for an agent.

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