teamleader_list_tasks

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only mentions 'optional filtering and pagination', which conveys basic read-only intent but does not disclose response format, default ordering, or any side effects. This is minimal transparency for a tool with no annotation support.

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, well-structured sentence that front-loads the action ('List tasks') and immediately follows with the key optional features. Every word earns its place with no wasted text.

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, the description should explain what the response contains, but it does not. It also lacks any usage guidance or alternative distinctions. The tool is simple, but the description leaves out essential context about return values, making it incomplete.

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 100%, with each of the 5 parameters already documented. The description adds no parameter-specific meaning beyond summarizing that filtering and pagination exist, so it does not boost the baseline score of 3.

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 'List tasks from Teamleader Focus', specifying the verb, resource, and scope. It distinguishes this tool from sibling list tools like teamleader_list_contacts or teamleader_list_deals by naming the exact entity (tasks).

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 gives clear context that the tool lists tasks, but provides no explicit guidance on when to use it versus alternatives or when not to use it. No alternative tools are mentioned, so usage is implied rather than explicitly directed.

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