Get Tasks For Contact

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

With no annotations, the description discloses important behavioral traits: full task fields are returned per result, and count_only=true auto-paginates and returns only counts/breakdowns. This goes beyond a basic 'retrieve' but does not cover pagination details or potential side effects.

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?

Three sentences, each adding distinct value: the core action, the full-data guarantee, and the count_only tip. The information is front-loaded and concise with no fluff.

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 list tool with no output schema and no annotations, the description covers the main use case and the count_only mode. It does not explicitly explain pagination behavior for non-count calls, but the schema provides page and max_results parameters, making it adequately complete.

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% with detailed parameter descriptions. The description adds value by advising to use count_only=true for accurate counts, reinforcing the parameter's purpose 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 clearly states the tool retrieves all tasks for a specific contact, using a specific verb ('Retrieve') and resource ('tasks'). It is distinguishable from siblings like get_task (singular) and search_tasks (search-oriented).

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 explicitly explains that full task data is returned so there is no need to call get_task afterward, and recommends count_only=true for accurate counts. However, it does not discuss when to use search_tasks or other alternatives.

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