Search tasks

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing behavioral beyond that – no pagination defaults, result limits, sort behavior, or auth requirements – leaving the extra context the annotations don't cover undisclosed.

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?

One compact sentence naming the filters plus a short illustrative example. Zero waste, front-loaded with the core capability, and every clause earns its place.

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 9-parameter read-only tool with no output schema and no annotations about returns, the description covers the searchable dimensions but omits pagination behavior (default 20, max 200) and sorting guidance. Adequate, but an agent must open the schema for anything beyond the high-level purpose.

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 78%, so the schema does most of the work; baseline is 3. The description maps four concepts (owner, status, due date, related deal) onto assignee_ids, statuses, due_before/after, and opportunity_ids, which adds modest conceptual framing but no syntax or format detail 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?

States a specific verb (Search) and resource (tasks) plus the filterable dimensions (owner, status, due date, related deal). It is clearly distinguishable from write siblings like create_task and complete_task, though it does not explicitly name a sibling search tool to differentiate from.

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 quoted example "what's overdue for me?" implies the intended use case (filtering by assignee plus due date), which is helpful context. However, there is no explicit when-to-use/when-not guidance and no mention of alternatives, so usage is only implied.

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