get_deal_pipeline

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

No annotations are provided, so the description carries the full burden. However, it only states the action and does not disclose potential error behavior, permission requirements, or explicitly confirm that this is a read-only operation beyond the verb 'Get'. It adds no behavioral context beyond the tool name.

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 extremely concise: one main sentence and a single parameter explanation, with no redundant words. It is front-loaded and well-formatted, earning its place despite its brevity.

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?

The tool is simple (one parameter, output schema exists), so the description is mostly adequate for an agent to invoke it correctly. However, it lacks explicit behavioral context such as error conditions or read-only confirmation, which a complete description might include, especially given the absence of annotations.

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 schema has 0% description coverage, but the description adds a brief explanation of pipeline_id as 'The Nimble pipeline ID,' which provides some context beyond the schema's title 'Pipeline Id'. It clarifies the namespace but does not offer format details, examples, or how to obtain the ID.

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 the specific verb 'Get' with the resource 'single deal pipeline' and the scope 'by ID', clearly distinguishing it from list/create/update/delete pipeline siblings. It exactly matches the tool name and leaves no ambiguity about what it does.

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 implies usage when you have a specific pipeline ID, but it does not explicitly mention alternatives or exclusions. For example, it does not say to use list_deal_pipelines for retrieving all pipelines, so the guidance is implied rather than spelled out.

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