collection_list

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

The description implies a read operation through the word 'lista' (list) and optional filtering, but it does not explicitly confirm read-only status, permissions, or side effects. Since no annotations are provided, the description carries the burden and offers only basic behavioral clues.

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 sentence that immediately conveys the main action and the optional filter. It is concise and front-loaded, with no unnecessary words or information.

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 the absence of an output schema, the description should explain what is returned (e.g., a list of request objects with properties). It does not, leaving the agent unaware of the structure or fields of the result, which is a significant gap for a simple tool.

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 already describes the 'tag' parameter with 100% coverage, and the tool description merely repeats 'Opcionalmente filtra por tag' without adding any new meaning or format expectations. This meets the baseline but adds no value beyond the schema.

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 tool lists all requests in the collection, which is a specific action. However, it does not differentiate itself from sibling tools like 'collection_get' or 'api_endpoints', which might also list items.

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 provided on when to use this tool versus alternatives such as 'collection_get' or 'request'. The description only mentions an optional filter, without explaining why one would choose this over other listing tools.

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