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

Annotations already declare readOnly/idempotent/openWorld, but the description adds substantial context those fields cannot: the billing model ('Charged only when the answer is delivered'), the exact cost ($20.00 per call), the 20-step budget, and the full response shape including per-step tool traces and sources. This is exactly the behavioral detail an agent needs to judge cost and trust before invoking.

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 a single dense paragraph that leads with the core promise, then examples, step cap, billing, inputs, and return shape. It is information-rich and nothing is gratuitous, though the trailing 'Returns:' enumeration is long and slightly crowds the routing information an agent most needs up front.

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?

With a full output schema present, the description needn't enumerate return fields yet does so helpfully, and it covers cost, step budget, and inputs. The only real gap is tier selection among the three agent_task variants, which is the one thing an agent cannot derive from structured data.

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 description coverage is 100% and all four parameters are already documented in the schema. The description restates them ('task; optional context, fields for a JSON answer, language') but adds no format, default, or constraint detail beyond what the schema provides, so the baseline of 3 applies.

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 a concrete verb and resource ('hand it any task in plain words and get the finished result in one call') and enumerates the task families it handles (research, website check, screening, markets, comparison, fact-pulling). The title 'the hardest tasks' plus the 20-step cap and $20 price distinguish it from the sibling hubvibe_agent_task and hubvibe_agent_task_pro tiers.

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?

The description implies the tier through 'the hardest tasks', the 20-step ceiling, and the $20 price, but never explicitly states when to choose this over hubvibe_agent_task_pro or hubvibe_agent_task. There are no exclusions or routing rules, even though three near-identical siblings exist, leaving the agent to infer the escalation condition.

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