bunny_get_edge_script_code

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that the payload is JavaScript source code, but it discloses no further behavior such as response shape or whether unpublished scripts are retrievable. It does not contradict the annotations.

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?

One sentence with a clear verb, direct object, and no filler. The core information is front-loaded, making it easy for an agent to parse quickly.

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 one-parameter, read-only getter, the description and schema together are almost sufficient. A note on the exact return format would be helpful because there is no output schema, but the intended payload 'source code' is clear enough. Minor gap is the lack of contrast with the sibling get_edge_script tool.

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 documents the single id parameter as an Edge Script ID with exclusiveMinimum >0, so description coverage is 100%. The description adds no extra meaning beyond what the schema already provides, meriting the baseline score.

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?

States a specific verb (retrieve) and resource (JavaScript source code of an edge script), making its purpose immediately clear. It distinguishes itself from sibling bunny_get_edge_script by targeting the code payload rather than general script metadata.

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 wording implies this tool is for reading an edge script's source code, but it does not explicitly say when to use it over bunny_get_edge_script or set_edge_script_code. Guidance is only implied, not stated.

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