pylon_list_collections

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

No annotations are provided, so the description must carry full burden. It only states the basic action and scope, without disclosing any behavioral nuances such as pagination, access restrictions, error handling, or return format. This is comparable to the update_drive example that scored 2 for lacking permission/side-effect details.

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 concise sentence with no filler. It front-loads the verb and resource, making it immediately clear and easy to scan.

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?

With only one parameter and no output schema, the description is minimal but adequate for a simple list operation. However, it lacks details about return format, pagination, or behaviors on invalid IDs, leaving some gaps for an agent to resolve.

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 100% for knowledge_base_id, so the schema already documents the parameter. The description adds no extra parameter semantics beyond what the schema provides, meriting the baseline score of 3.

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 uses a specific verb 'List' plus resource 'collections' and scope 'in a knowledge base', clearly distinguishing it from sibling tools like pylon_get_collection (single collection) and pylon_list_knowledge_bases (different resource).

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 clearly indicates when to use this tool (to list collections for a given knowledge base) and the required knowledge_base_id parameter is obvious. However, it does not explicitly mention exclusions or alternatives, such as using pylon_get_collection for a single collection.

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