script_read

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only operation but says nothing about what happens if the file is missing, whether the full source is returned or truncated, or what access/permissions are needed.

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?

A single short sentence with the operation front-loaded and no wasted words. It is efficient, though arguably too terse to be genuinely helpful.

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?

With no annotations and no output schema, the description should at minimum explain the return shape and the parameter format, and it explains neither. The unexplained duplication with the 'read_script' sibling also leaves routing unresolved.

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 0% for the single required 'target_file' parameter, so the description must compensate and does not. It gives no hint of the expected path format (instance path like 'game.Workspace.Foo', file path, or name), leaving the agent to guess the identifier syntax.

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 ('reads') and resource ('a script') with a scope ('from the Roblox workspace'), so the basic operation is unambiguous. However it does nothing to distinguish itself from the sibling 'read_script', which appears to perform the identical function, so it fails the sibling-differentiation bar for a 5.

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?

There is no guidance on when to use this tool versus the near-identical 'read_script' sibling, nor any prerequisites or exclusions. An agent has to guess which of the two read tools is correct.

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