list_containers

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

With no annotations, the description carries full burden. It mentions pagination and filtering but does not disclose read-only nature, permissions, rate limits, or maximum pagination limits. Barely adds behavioral context.

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, front-loaded with the verb 'List', no redundant words. Efficiently conveys the core action and scope.

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?

No output schema; 5 parameters with no descriptions. The description only covers pagination and filtering superficially. Missing details on return format, error handling, or behavior with empty results. Incomplete for a tool of this complexity.

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 schema has 0% coverage meaning no individual parameter descriptions. The description vaguely mentions 'pagination and filtering' but does not explain which parameters correspond to these features (limit/offset for pagination; service, fields, include_deleted for filtering). Adds minimal value beyond schema titles and defaults.

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 verb 'list' and resource 'containers from OpenMetadata' with features 'pagination and filtering'. It is specific and distinguishes from other tools by resource type, though sibling list tools exist for other entities.

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 usage for listing with pagination and filtering but provides no explicit when-to-use guidance or alternatives like get_container or create_container. It is adequate for basic context but lacks exclusions.

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