lookup_pipelines

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

No annotations provided, so description carries full burden. It describes the lookup behavior and workflow, but does not explicitly state that it is read-only or mention authorization needs. However, the context (lookup) implies read-only.

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?

Well-structured: purpose, usage guidelines, parameter details. Slightly verbose but every sentence adds value. Could be slightly more concise, but is clear and 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?

No annotations or output schema details, but description covers the essential workflow. Sibling tools are listed, and the tool's role is clear. Missing some details like permissions or error cases, but sufficient for basic use.

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?

Despite 0% schema coverage, the description details all four parameters: query (format and behavior), entity_type (default LEAD), page (0-based), size (max 50). This fully compensates for missing schema descriptions.

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 'Look up pipelines by name (for leads)' and specifies when to use it: 'when the user asks for leads by stage but does not specify which pipeline.' It distinguishes itself from sibling tools like get_pipeline_stages.

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?

Explicit step-by-step instructions: 'Call this first; do NOT call get_pipeline_stages until after the user confirms.' Describes when to call and what to do with results (present, ask confirmation).

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