get_script_code

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It indicates a read operation ('get') and that the full code is returned, but does not disclose potential errors, authentication requirements, or side effects. For a simple getter, this is acceptable but not rich.

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 short sentences, the first stating the core functionality and the second giving the usage context. No redundant phrasing or filler, making it 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 tool with a single simple parameter and no output schema, the description adequately covers what it does and when to use it. The return value is implied ('full code'), which satisfies the need without an output schema. It is sufficiently complete for the low complexity.

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 100%, with the single parameter script_id described as 'Script ID'. The description adds 'by ID' which is redundant with the schema, providing no additional semantic value beyond the schema. Baseline 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 'Get the full code of a script by ID', which is a specific verb (Get) and resource (script code) that distinguishes it from sibling tools like get_script (which likely retrieves metadata) and other get_*_code tools for different entity types. The purpose is unambiguous.

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?

Includes explicit usage guidance: 'Use this when you need to read or analyze the script code.' This tells the agent when to invoke it, though it does not mention alternatives or when not to use it, preventing a 5.

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