bunny_list_edge_scripts

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

Annotations already establish the read-only, idempotent, non-destructive safety profile. The description adds account-wide scope and domain context, but does not disclose behavioral details such as pagination, ordering, or response shape. This matches the lowered bar for annotations but adds limited behavioral information.

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?

Two sentences with the operative instruction and scope front-loaded. The second sentence provides only a brief, useful definition of the resource, and there is no filler or repetition of schema/annotation 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?

For a zero-parameter, read-only list operation with robust annotations, the description provides all necessary orientation: account-level enumeration and what an edge script is. No output schema exists, but the purpose of the tool makes the list-shaped return value obvious, so nothing critical is 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?

The schema has zero parameters and 100% description coverage, so the baseline is 4. The description correctly avoids inventing parameter behavior and needs no parameter-level documentation.

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 uses a specific verb ('List'), names the resource ('Bunny Edge Scripts'), and scopes the operation to 'the account'. This clearly distinguishes it from sibling single-resource tools like bunny_get_edge_script and bunny_manage_edge_script, and the added explanation clarifies what edge scripts are.

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?

'List all … in the account' gives a clear context for when to use this tool: when the agent needs to enumerate edge scripts across the account rather than retrieve, publish, or manage a specific one. However, it does not explicitly name alternatives or state when-not-to-use this tool, stopping short of a 5.

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