aap_list_collections

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds the endpoint '/api/automation-hub/v3/' and return format 'str: JSON', which are useful context beyond annotations. No contradictory behavior is disclosed.

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 compact paragraph with separate Args and Returns sections. Every sentence contributes purpose, a prerequisite, and return info. No redundant filler.

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 simple read-only list tool, the description covers purpose, API access requirement, and return type. The input schema provides parameter details, and annotations cover safety. It lacks explicit pagination behavior, but the schema defaults and descriptions are sufficient.

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 description only says 'params (ListCollectionsInput): Pagination and filter.' It does not explain the individual fields like page, search, namespace, or page_size. With schema coverage at 0%, the description should compensate, but it only provides a high-level grouping.

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 states 'List Ansible collections in Automation Hub' – a specific verb, resource, and location. This clearly distinguishes from sibling list tools like aap_list_projects or aap_list_inventories.

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 when the agent needs collections from Automation Hub, and the API-access note provides a prerequisite. However, it doesn't explicitly state when not to use it or mention alternatives, though the context is clear enough.

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