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; description adds behavioral details: script proxy encoding, client-side-only requirement for scriptGetterSource, line range behavior. Could mention error handling or return format but sufficient.

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 concise sentences: first states purpose and methods, second gives practical usage hint. No unnecessary words.

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?

Covers multiple specification methods and parameter usage. No output schema, but return format is implied (decompiled source). Missing explicit note on return type or error behavior, but sufficient for a simple retrieval 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?

Schema coverage 100%; description adds context: startLine/endLine usage hint, warning about HTML encoding for scriptPath, and client-side restriction for scriptGetterSource, enriching 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?

Clearly states verb 'Get' and resource 'decompiled source for a Roblox script' with three methods (path, script proxy, getter code). Distinct from sibling tools like 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?

Provides guidance on when to use startLine/endLine for large scripts. Mentions the three ways to specify the script. No explicit when-not or alternatives, but given sibling list, it's the only script content tool.

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