search_tasks

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

No annotations provided, so the description carries full burden. It discloses pagination, AND logic for filters, and default behavior with no filters. It could mention sort order or limit behavior, but covers key traits.

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?

Short, three sentences with clear structure: first sentence states purpose, second gives usage rules, third provides additional context. No unnecessary words.

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 9 optional parameters and an output schema, the description covers the general search behavior well but lacks full parameter documentation. The output schema compensates for return values, but parameter details are incomplete.

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 has 9 parameters with 0% description coverage. The description mentions title, date range (implies multiple date params), and owner_id, but does not explicitly list all parameters or their relationships. The limit parameter is omitted, reducing clarity.

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 the verb 'Search' and the resource 'tasks', with specific filters (title, date range, owner). It distinguishes from sibling search tools by explicitly targeting tasks and describing the filtering logic.

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?

Provides explicit guidance: require at least one filter, AND logic, no filters returns paginated recent tasks, date format YYYY-MM-DD, and references list_users for owner_id. This helps an agent decide when and how to use it.

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