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

Annotations only declare readOnlyHint=false, so the description carries real weight and delivers: the task goes live immediately (side effect), requires the tasks:write scope (auth), and is bounded by account limits. It does not address reversibility/cancellation, so not a 5.

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 tight sentences with the core purpose front-loaded and constraints second. No filler, though slightly dense with parenthetical list of limits.

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?

For a 12-parameter mutation tool with no output schema, the description covers purpose and side effects adequately but leaves most parameter semantics and the dry_run validation option unexplained. Adequate, not complete.

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 12 parameters and only 33% schema description coverage, the description must compensate but largely does not. It gestures at amount, category, and country via the limits sentence, but says nothing about address, task_type, start_date, estimated_hours, or the useful dry_run flag.

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 specific verb and resource ('Post a task') and clarifies it is posted on behalf of the human and goes live immediately. This clearly distinguishes it from bidding (bid_on_task) or offering services, though it does not name a sibling explicitly.

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 conveys context (goes live like an in-app task) and preconditions (scope, limits), but never states when to use this versus alternatives such as offer_service or how it relates to search_tasks/get_task. Usage is implied rather than guided.

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