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

The readOnlyHint annotation already establishes a safe read profile. The description goes beyond that by disclosing the return envelope ('Returns {count, results}'), which matters because there is no output schema, and by mapping to the underlying GET /tasks endpoint. It does not mention pagination limits or auth needs, but for a read-only tool that is a minor gap.

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 compact burst of front-loaded information: purpose, scoping options, filter example, return shape, endpoint. Every clause earns its place and nothing is padded.

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?

With no output schema, the description usefully declares the {count, results} return shape, and the filter/related_id/pagination semantics live in the schema. What is missing is guidance on default result volume or how count relates to pagination, but the definition is sufficient to call the tool correctly.

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 the baseline is 3. The description adds value by supplying a task-specific filter example ({'must':[{'term':{'is_completed':false}}]}) that goes beyond the generic examples in the schema, and it restates related_id's contact/job scoping in prose.

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 and resource ('List tasks and appointments') and clarifies the scope includes appointments, which helps distinguish it from list_activities or list_contacts. However, it never explicitly differentiates itself from sibling list tools, so an agent must infer the routing from the resource name alone.

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?

It implies two usage modes - scope by related_id or apply a filter - and gives a concrete filter example for open tasks, which is helpful context. It does not state when to prefer this over list_activities or get_task, nor any prerequisite/constraint on when filtering is required.

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