list_managers

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

There are no annotations to provide behavioral context, and the description adds little beyond the basic list operation. It does not disclose behaviors such as whether deleted managers are included, how pagination behaves, ordering, or rate limits. The agent is left without crucial information about the tool's runtime behavior.

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, clear, front-loaded sentence that conveys the core purpose without any unnecessary words or repetition. It is highly concise and well-structured.

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 pagination parameters and no output schema, the description is minimally adequate. However, the phrase 'List all managers' could mislead an agent into thinking it receives every manager in one call, when in reality the limit/offset pagination means multiple calls may be required. More detail about pagination behavior and returned fields would improve completeness.

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 provides full descriptions for both 'limit' and 'offset' parameters (100% coverage). The description does not add additional meaning to these parameters, but since the schema handles the heavy lifting, the 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 all managers in the AdButler account, using a specific verb ('List') and resource ('managers'). It distinguishes from 'get_manager' by explicitly indicating the scope is 'all' managers rather than a single entity.

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 explicit guidance is provided about when to use this tool versus alternatives like 'get_manager'. The description only states what the tool does, not in what scenarios it should be preferred, nor does it mention pagination or when the limit/offset parameters would be needed to retrieve all results.

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