list_tasks

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

Annotations already provide readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds further behavioral context beyond annotations: the default status, optional owner narrowing, and the endpoint's missing due-date filter. It does not cover pagination behavior or response details, preventing a 5.

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 tight sentences. The first sentence states the action, the second conveys defaults and filters, and the third calls out a relevant API limitation. Every sentence earns its place with no redundancy.

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 read-only list operation, the description plus schema cover the default behavior, filtering options, pagination parameters, and a well-advertised endpoint limitation. The lack of an output schema is not a meaningful gap for this kind of listing tool.

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?

The schema already documents status and ownerId with descriptions, and the description mostly paraphrases those rather than adding new semantic meaning. page and perPage have schema defaults and constraints but no descriptive semantics, and the description does not clarify them. So it lands at the adequate baseline without fully compensating for the 60% schema coverage.

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 operation: listing tasks in Capsule CRM. It also establishes the default scope (OPEN tasks) and the distinct owner filtering capability, making it unambiguous next to sibling task and filter tools.

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 gives concrete when-to-use guidance: default to OPEN, pass status to broaden, and filter by owner via ownerId. It also explicitly names the limitation (no due-date filter) and tells the agent to use filter_* tools or iterate instead, which is strong alternative routing.

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