list_api_collections

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

With no annotations, the description carries the full burden for behavioral disclosure. It only provides the verb 'List' and a definition of the resource; it does not disclose return format, pagination, ordering, permission requirements, or any potential side effects. This is a significant gap for a tool with no output schema.

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, front-loaded with the verb and resource, and uses a dash to add a concise explanation. Every word contributes to understanding the tool's purpose, with no wasted content.

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 list tool with no parameters and no output schema, the description is mostly complete. It states what is listed and clarifies the resource type. However, it does not mention the output shape or any permission/scope constraints, which would be helpful but are not critical given the low complexity. Overall, it is adequate and useful.

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 tool has zero parameters, so the baseline is 4. The description adds contextual meaning by explaining what an API Platform collection is, but there are no parameter details to provide. This is appropriate for a parameterless tool.

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 'List API Platform collections' with a specific verb and resource. The appended clause 'each is an API product that can be exposed as a Workato MCP server' distinguishes this from the sibling list_mcp_servers, which lists MCP servers themselves. This makes the purpose unambiguous and well-differentiated.

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 its usage (listing API Platform collections) but does not explicitly state when to prefer it over alternatives like list_mcp_servers or create_api_collection. There is no mention of exclusions or when-not-to-use. Thus it provides clear context but no explicit guidance.

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