get_pipeline_generation_rules

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

With no annotations provided, the description carries full behavioral transparency burden. It explicitly discloses that the tool returns 'Complete Markdown specification text to guide pipeline JSON creation' and enumerates the content types (validation rules, node hierarchies, schema guidelines). This gives clear expectations of a read-only retrieval operation, though it doesn't mention potential authentication requirements or caching behavior, which are minor for this simple getter.

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 long, with the first sentence front-loading the core purpose and content, and the second specifying the return format. Every word earns its place, and there is no fluff or repetition of schema details.

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 zero-parameter, read-only tool that returns rules, the description is complete. It covers what the tool does, what content is included, and the return format. No output schema is required since the return is a Markdown text specification, and the sibling tools provide surrounding context for when this would be used.

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 tool has zero parameters, so the schema is fully complete with 100% coverage. The description adds value by explaining what the returned specification contains, which is useful context beyond the empty schema. Since there are no parameters, the baseline for zero-param tools is 4, and the description meets that by enriching the tool's purpose without needing parameter details.

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 the official specification, validation rules, node type hierarchies, and schema guidelines for generating Colba pipeline JSON configurations. This specific verb+resource combination distinguishes it from sibling tools like create_pipeline or list_pipelines, which operate on pipeline instances rather than the generation rules.

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 the tool is used when generating new pipeline JSON configurations, but it doesn't explicitly state when to use it over alternatives or provide exclusions. Sibling tools like create_pipeline are clearly for pipeline creation, making the use case inferable, but the absence of explicit when/when-not guidance keeps it at an implied level.

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