listSitesStacks

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

No annotations provided, and the minimal description does not disclose behavioral traits like pagination behavior, authentication requirements, or potential side effects. Only states basic listing action.

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, no filler. Could be considered too brief, but for a simple list tool it is concise. Front-loaded with the action 'List switch stacks in a site.'

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?

Tool has 4 parameters including pagination and no output schema. The description does not mention pagination, return format, or handling of defaults (e.g., siteId from config). Incomplete for a list operation with pagination.

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 covers all parameters with descriptions (100% coverage), so the description adds no extra meaning beyond what the schema provides. Baseline score of 3 is appropriate.

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 switch stacks in a site. It is specific with verb and resource, but does not explicitly differentiate from sibling tools like getSwitchStackDetail or listSwitchNetworks.

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 on when to use this tool versus alternatives such as getSwitchStackDetail (for a single stack) or listSwitchNetworks (for networks). Does not mention prerequisites or when not to use.

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