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

With no annotations, the description must carry the full behavioral burden. It only states that it lists pipelines, but does not disclose what the output format is, whether results are paginated, or how the 'format' parameter affects behavior. This leaves the agent guessing about the tool's actual behavior.

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 a single short sentence, which is concise and front-loaded with the main action. No unnecessary words are present. However, it lacks supporting details about parameters or output, so it is not as complete as it could be while remaining concise.

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 that there is no output schema, no annotations, and an undocumented parameter, the description is too thin. It does not clarify the return structure or the meaning of the 'format' parameter, making the tool under-specified for an agent that needs to invoke it correctly.

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 input schema defines a 'format' parameter with a default of 'summary', but the description provides zero explanation of it. With 0% schema description coverage, the agent has no idea what values are acceptable or what 'summary' vs. other formats would return. The description does not compensate for this 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 the action and resource: 'List all pipelines from Cycloid.' This is specific enough to distinguish from sibling tools like CYCLOID_BLUEPRINT_LIST or CYCLOID_CATALOG_REPO_LIST, which target different entity types.

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 is given about when to use this tool versus alternatives. The description does not mention prerequisites, expected use cases, or exclusions such as filtered listing. The agent has to infer the purpose from the name alone.

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