get_pipeline_leads

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

With no annotations provided, the description carries the burden of behavioral disclosure. It states that the tool retrieves contacts/leads per pipeline and optionally filters by stage, which is useful. However, it does not mention pagination, ordering, or what happens when no stage is provided—though these are somewhat implied by the optional filter and the limit parameter.

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 two sentences: a clear definition followed by two practical examples. Every word earns its place; there is no redundancy or fluff.

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 read-style tool with no output schema, the description is sufficient to understand the tool's scope and use. The examples make the intended usage concrete, and the schema covers all parameters. A minor gap is the lack of any note about default limit or response shape, but it is not critical for such a straightforward query 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 input schema documents all three parameters with 100% coverage, so the baseline is 3. The description adds modest value by clarifying the semantics of 'pipeline_id' (a specific pipeline) and 'stage' (optional filter), but it does not add any format details beyond the schema. The example usage reinforces the parameters but does not introduce new meaning.

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 uses a specific verb ('Get') and resource ('contacts/leads in a specific pipeline'), clearly distinguishing it from siblings like list_contacts (all contacts) and get_contact (single contact). The optional stage filter is also stated, making the purpose 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 clearly implies when to use this tool: when you need leads/contacts scoped to a specific pipeline, optionally filtered by stage. The examples ('Show leads in my Sales pipeline' / 'Who is in the Negotiation stage?') reinforce the intended use case, though no explicit exclusions or alternatives are named.

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