List Tasks

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

Annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true) already declare safety. The description adds specific behavioral details: default top 50, max 300, pagination support, and available expand options. This provides useful context beyond annotations without contradiction.

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 three sentences with no wasted words. The first sentence states the core purpose, the second lists capabilities, and the third details expand options. Information is front-loaded and efficiently organized.

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?

Given 6 optional parameters and no output schema, the description covers filtering, sorting, pagination (with defaults), field selection, and expand entities. It includes constraints like max top. Minor omissions: no mention of response format or error behavior, but overall sufficient for a 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?

Schema coverage is 100%, but the description adds meaningful examples for filter (e.g., 'DealId eq 456', 'Finished eq false') and lists expand options beyond the schema's abbreviated list. This enhances agent understanding of how to construct effective queries.

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 'Search and list tasks in Ploomes CRM' with specific capabilities like OData filtering, sorting, field selection, and pagination. It lists filterable fields and expand options, distinguishing it from sibling tools like ploomes_tasks_get (single task) or ploomes_tasks_create (create).

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 listing tasks with various filters, but does not explicitly state when to use this tool over alternatives (e.g., ploomes_tasks_get for single task, ploomes_tasks_list for all tasks without filters). No exclusions or when-not-to-use guidance is provided.

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