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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description goes beyond them by enumerating the payload contents (active script, versions, settings) — meaningful given there is no output schema — though it says nothing about size, versioning behavior, or what happens when no script exists.

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?

Very short and dense: payload contents first, then the user-facing directive. The parenthetical field list is slightly cluttered but every element carries information; no filler sentences.

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 single-parameter read tool with full annotation coverage, the description covers what it returns and when in the workflow to invoke it. With no output schema, a bit more detail on the returned shape (e.g. empty/absent script case) would be needed for a 5, but nothing essential is missing.

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 is 100% with a single project_id parameter, so the schema already carries the parameter documentation. The description adds no additional meaning about project_id (format, source, or scoping), which is the expected baseline when the schema does the work.

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?

Names the exact resource returned — the active script, its versions, and script settings with three named setting fields — so an agent knows precisely what this fetches. It is phrased as a noun list rather than a verb+resource statement, but the read intent is unambiguous and it is distinguishable from script_edit and script_generate by naming script content rather than changes.

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?

"Show the script to the user before Analyze Script" supplies one workflow cue and a sequencing constraint, which is real guidance. However, it never names the sibling tools (script_edit, script_generate) or states when-not to use this versus those, so the routing information is only partially implied.

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