teamleader_list_deal_sources

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

With no annotations, the description carries the behavioral burden. 'List' and 'find source_id' imply a read-only operation that returns source identifiers, but it does not describe response shape, pagination behavior, ordering, or error conditions. It is not misleading, but it is minimally informative.

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?

Two short sentences with no filler: the first names the operation and the second gives the actionable use case. It does not repeat schema details and is easy to scan.

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 simple list tool with optional pagination parameters and no required arguments, the description covers why and when to call it. The lack of an output schema is partially mitigated by the explicit source_id guidance, though response format details are not described.

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%: both page and page_size have clear descriptions with defaults and limits. The tool description adds no parameter-level meaning beyond that, so the baseline score 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 identifies the resource (deal sources), uses the clear verb 'list', and explains the practical purpose: finding source_id for deal creation/update. It does not explicitly differentiate from sibling list_* tools, but the resource name and stated use case make the intent unambiguous.

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 a clear context for use: 'Use to find source_id when creating/updating deals.' It does not mention exclusions or alternatives, but for a simple reference-data lookup this is sufficient guidance.

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