list_configurations

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description contributes the ownership-scoping behavior, which is useful, but says nothing about ordering, whether full config bodies or summaries are returned, or how pagination behaves.

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?

A single front-loaded sentence with no filler. However, its brevity is also the source of the missing pagination and return-shape context, so it's efficient but arguably undersized for the job.

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?

There is no output schema, so the description should indicate what a listed configuration contains (summary vs. full body) and how results are truncated. With zero parameter documentation as well, the definition leaves real gaps for an agent that must paginate through results.

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%: skip and limit have types/defaults/bounds in the schema but no textual explanation, and the description adds nothing about pagination. With 0% coverage the description was expected to compensate and does not.

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?

States a specific verb (List) and resource (saved pipeline configurations) with an ownership scope ('the caller's own'). This clearly distinguishes it from get_configuration (singular fetch) and list_datasets, though it doesn't explicitly name those siblings.

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 caller's own' implies a scope restriction, suggesting it won't return shared or team-wide configurations, but no when-to-use guidance or named alternatives (e.g. get_configuration for a single item) is given. Usage is inferable rather than stated.

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