get_pipeline_details

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

With no annotations, the description carries full burden. It lists what is returned but does not disclose error handling, performance, or authentication needs. For a read operation, it is adequate but not exemplary.

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 well-structured with a lead sentence, argument breakdown, return list, and usage note. It is reasonably concise, though the return fields could be summarized more succinctly.

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?

Given the low complexity (2 params, no enums, no output schema), the description explains the return structure in detail and provides usage context. It lacks mention of potential errors but is sufficient for the tool's scope.

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 adds meaning by explaining the slug originates from search_pipelines and that lang accepts 'en' or 'ru' with a default, compensating for the schema gap.

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 it retrieves full pipeline details including title, goal, steps, tools, instructions, prompts, and pricing, distinguishing it from sibling tools like search_pipelines which return a list.

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 specifies the slug should come from search_pipelines and indicates the tool is for providing a complete actionable plan, implying it's used after selecting a pipeline. It does not explicitly exclude other scenarios, but guidance is clear.

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