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

The readOnlyHint=true annotation already establishes that this is a safe read operation, and the description adds some behavior: it searches public tasks, the summary field is shorter, and keyed results include my_application and my_assignment. However, it does not explain authentication, pagination, defaults, or the practical effect of keyed versus unkeyed results.

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 very short and has no filler, but it is a cryptic semicolon-separated fragment rather than a clear, front-loaded statement. Its brevity comes at the cost of structure and readability.

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 search tool with nine optional parameters, five enums, and no schema descriptions or output schema, the description is far too incomplete. It omits defaults, filtering semantics, pagination, and return behavior, leaving much of the tool's operation to inference.

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 0%, and the description only partially explains the fields parameter by saying "summary" is shorter. The other eight parameters, including sort, limit, status, category, bounty filters, auto_accept, and allow_agents, receive no semantic explanation in either the schema or description.

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?

The description says "Public tasks" and the tool name is search_tasks, so the resource and scope are inferable, but no actual verb or search capability is stated. It does not clearly distinguish its purpose from get_task or explain what kind of task search is performed.

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?

There is no guidance on when to use this tool versus get_task or the other siblings, and no prerequisites or exclusions are given. The phrase "with a key" hints at an authentication condition but does not explain when or why an agent should use the keyed variant.

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