List tasks

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

Annotations already declare readOnlyHint and openWorldHint, so the description need not cover safety. It adds the behavioral detail of pagination and filter support, but does not explain default behavior, response format, or filter semantics beyond the generic phrase.

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?

The description is a single concise sentence, front-loaded with the verb and resource, with no redundant words. It is appropriately sized for a simple listing operation.

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 10 optional parameters and only 10% schema coverage, the description leaves most functionality unspecified. It lacks information on filter semantics, pagination defaults, or any usage constraints, making it incomplete for an agent to confidently invoke with correct parameters.

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 description coverage is only 10% (one parameter has a description). The description mentions 'pagination and filters' but does not explain specific filter parameters or their meanings, failing to compensate for the sparse schema descriptions.

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 lists tasks and mentions pagination and filters, offering a specific verb+resource+scope. However, it does not explicitly differentiate from related tools like kommo_tasks_get, relying on the name for distinction.

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 implies usage for fetching task lists with pagination and filters, but provides no explicit guidance on when to use this versus alternatives like kommo_tasks_get or other list tools. No exclusions or alternative recommendations are mentioned.

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