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

Beyond readOnlyHint=true, it discloses that no credentials are needed, that no listing ever crosses a country border, that in-person tasks only appear when coordinates are supplied and only inside that country's radius, and that addresses are approximate and posters anonymized. Auth requirements, filtering exclusivity, and result composition are all covered.

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?

Four short sentences, zero filler, and the most consequential constraint (country as a hard boundary) is front-loaded immediately after the purpose statement. Every sentence carries a distinct, actionable fact.

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 an 11-parameter, no-output-schema search tool it covers the critical filtering semantics (country, location, anonymity), but leaves pagination, sorting behavior, budget filtering, and category/task_type selection undescribed. Adequate for the headline behavior, incomplete for full invocation.

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 coverage is 27% across 11 params, so the description must compensate and largely doesn't. It clarifies the semantics of country (hard boundary) and latitude/longitude (needed for in-person work), but says nothing about sort, limit, offset, search, category, task_type, or the budget filters, which the schema also leaves bare.

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 with scope: 'Search open tasks on Day1Work.' That is enough to separate it from get_task (single task) and post_task, but it never names or contrasts those siblings explicitly, so an agent still infers the boundary from the verb alone.

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?

Gives real conditional guidance: reading needs no credentials, country is mandatory and a hard boundary, and in-person results require latitude+longitude. It does not say when to prefer get_task or how this relates to other listing tools, so it stops short of full alternative routing.

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