tasks_search

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Search' implies a read-only operation, but the description doesn't clarify whether this is safe (non-destructive), what permissions might be needed, whether results are paginated, or what the response format looks like. It mentions 'specific filters' but doesn't explain how filtering works or any limitations.

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 extremely concise with just 5 words, front-loading the core purpose. There's no wasted language or unnecessary elaboration, making it easy to parse quickly.

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?

Given the complexity (5 parameters, nested filtering logic, no output schema, and no annotations), the description is inadequate. It doesn't explain the search functionality, parameter interactions, result format, or behavioral aspects. For a tool with rich filtering capabilities and multiple parameters, this minimal description leaves too many gaps for effective use.

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?

The schema has 5 parameters with 0% description coverage, meaning all parameters are undocumented in the schema. The description only vaguely mentions 'specific filters', which corresponds to the 'filterGroups' parameter but doesn't explain the other 4 parameters (properties, limit, after, sorts) or provide any syntax, format, or usage details. It adds minimal value beyond the 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 'Search tasks with specific filters' clearly states the verb ('Search') and resource ('tasks'), but it's vague about what 'specific filters' means and doesn't distinguish this tool from sibling tools like 'tasks_list' or 'tasks_get'. It provides a basic purpose but lacks specificity about what makes this search tool unique.

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?

No guidance is provided about when to use this tool versus alternatives like 'tasks_list' or 'tasks_get'. The description mentions 'specific filters' but doesn't explain what scenarios require filtering versus simple listing. There's no mention of prerequisites, alternatives, or exclusions.

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