search_tasks

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

It discloses a critical non-obvious behavior: the query parameter is applied client-side after each API page fetch, and has_more reflects API pagination rather than matching-result completeness. This goes well beyond the readOnlyHint and openWorldHint annotations, providing essential operational details.

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 efficiently structured: a one-line purpose, a critical note about pagination behavior, and a compact arg list. Every sentence adds value, and the format is front-loaded with the most important information.

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 complex tool with 9 parameters, an output schema, and annotations, the description fully covers usage semantics, behavioral caveats, and pagination. It is complete enough for an agent to use correctly without additional investigation.

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%, but the description compensates by explaining each of the 9 parameters in the Args list, including the client-side filtering semantics for query, date format expectations, page indexing, and defaults. This adds significant meaning beyond the bare schema.

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 clearly states 'Search tasks across the workspace' with a specific verb and resource, and the filtering capabilities distinguish it from sibling tools like get_task or get_list_tasks. It unambiguously identifies this as the general-purpose search/filter tool.

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 clearly implies when to use the tool (for searching tasks across the workspace with filters) and provides usage context, but it does not explicitly exclude alternatives or mention when not to use it. The hint to use get_current_user for assignee_id adds practical context.

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