teamleader_list_deals

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

No annotations are provided, so the description carries the behavioral burden. It discloses that filtering and pagination are supported, which is a minimal behavioral trait. However, it does not mention return format, ordering, default page size limits (beyond schema), authentication needs, or any other operational behaviors. This is adequate for a basic read-only list tool but lacks depth.

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 that front-loads the verb and object. It contains no redundant words and conveys the essential purpose without unnecessary detail.

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 tool with no output schema and no annotations, the description is somewhat minimal. It clearly states the purpose and capabilities but does not describe the response shape, default behaviors, or any relevant limitations beyond what the schema covers. There are clear gaps given the lack of structured metadata.

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 input schema fully documents all six parameters with descriptions, so schema coverage is 100%. The description adds no extra meaning beyond the schema, merely stating 'optional filtering and pagination' as a summary. Baseline of 3 is appropriate.

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 states a specific verb and resource: 'List deals/opportunities from Teamleader Focus'. It clearly distinguishes from single-deal operations like get_deal, create_deal, and update_deal, and the mention of optional filtering and pagination further clarifies its scope.

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 provides clear context: this tool is for listing deals with optional filters and pagination. However, it does not explicitly name alternatives or state when-not-to-use cases. The sibling tool names (e.g., get_deal for single deal) imply the distinction, but it is not made explicit.

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