Get the content of a script in the Roblox Game Client

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It does not mention side effects, error handling, permissions, or performance characteristics. The read-only nature of fetching decompiled source is implied but not stated, and there is no mention of what happens on failure.

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 two sentences long, front-loaded with the main purpose, and contains no filler. Every sentence adds value, making it efficient for an AI agent to parse.

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?

The tool has no output schema and no annotations. The description does not explain the return format (decompiled source structure) or clarify that at least one of scriptGetterSource or scriptPath is needed despite no required parameters. This leaves important gaps for an AI agent.

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%, providing baseline at 3. The description adds value by explaining how to use scriptPath with literal angle brackets for script proxies and that scriptGetterSource must be client-side. This extra context goes beyond the schema descriptions.

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's purpose: 'Get decompiled source for a Roblox script by path, script proxy, or getter code.' It uses a specific verb ('Get') and resource ('decompiled source'), and distinguishes three input methods. This clearly separates it from sibling tools like 'execute' or 'script-grep'.

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 description provides guidance for using startLine/endLine for large scripts, but does not explicitly compare this tool to alternatives or state when not to use it. Given the sibling list, this is the only tool for retrieving script content, so usage context is implied but not fully explicit.

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