list_pipelines

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

No annotations provided. Description mentions pagination and filtering but does not disclose how these work, what order results are returned, whether there are rate limits, or how include_deleted affects results. Agent needs more details to understand behavioral boundaries.

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?

Single sentence is concise and front-loaded. However, it lacks any structural breakdown or additional details that would improve usability. Could be expanded without losing its efficient nature.

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?

Tool has 5 parameters, no output schema, and no annotations. Description is too minimal; does not cover pagination implementation (limit/offset usage), filtering by service, or return format. For a list tool, more context is needed to ensure correct invocation.

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?

Schema description coverage is 0%. Description only mentions 'pagination and filtering' but does not explain any parameter (limit, offset, fields, service, include_deleted). Without any parameter explanation, the agent cannot use the tool effectively.

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?

Description clearly states the verb 'List', resource 'pipelines', source 'OpenMetadata', and features 'pagination and filtering'. This distinguishes it from sibling tools like get_pipeline (single item) and create_pipeline (create operation).

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?

No guidance on when to use this tool vs alternatives like get_pipeline or search_entities. Does not specify that this is for browsing all pipelines with pagination and filtering, while get_pipeline is for retrieving a specific pipeline by name.

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