List Sites

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

No annotations are provided, so the description carries the full burden. It mentions only that the tool lists sites and adds a scope, but it does not disclose whether this is a read-only operation, how pagination behaves, or what the response looks like. The presence of page/page_size parameters is ignored.

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, efficient sentence with no filler. It is appropriately short for a simple list operation, though it is so minimal that it leaves important behavioral and parameter context unaddressed.

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 no output schema, no annotations, and no parameter descriptions, the description is incomplete for someone needing to invoke the tool correctly. The agent can infer basic behavior, but pagination details, return shape, and alternative selection are missing.

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 0%, so the description must compensate, but it does not explain page or page_size. The parameter names and defaults suggest standard pagination, but there is no clarification of limits, indexing, or how these values affect results.

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 a specific verb ('List'), a resource ('sites'), and a scope ('this controller manages'). It is clear and distinguishable from siblings like call_operation or search_operations, though it does not explicitly differentiate from the similarly named list_devices.

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 given about when to use this tool versus alternatives. The sibling list_devices exists, but the description does not explain when to choose list_sites over list_devices or any other operation.

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