tududi_search_tasks

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

No annotations provided and description is minimal. Does not disclose behavioral traits such as how results are returned, pagination, or any side effects. With no annotations, description carries full burden but provides no additional behavioral context.

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?

Single sentence, concise but lacks substance. For a tool with 5 parameters and no output schema, more detail is needed. It is not appropriately sized for the complexity.

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 5 parameters, no output schema, and no annotations, the description is too minimal. It does not explain how filters combine, default behavior, or what the return value is. Incomplete for the tool's complexity.

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 100%, so parameters are already described. Description adds no extra meaning beyond 'with filters'. No need for additional details as schema is sufficient, but no added value.

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?

Clearly states it is for searching tasks with filters, but does not differentiate from 'tududi_list_tasks' which also lists tasks. Lacks sibling distinction for top score.

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 on when to use this tool vs alternatives like 'tududi_list_tasks'. No context on when to apply filters or when not to.

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