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

Annotations already cover safety (readOnly, non-destructive, closed-world), so the description adds real value beyond them: it discloses that the full body is returned and that bodies contain {first_name} and {company} placeholders substituted per recipient at recording time. That materially affects how an agent should present or reuse the content.

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, front-loaded with what is returned, then the placeholder caveat. No waste, though the placeholder note is the only real payload in the second sentence.

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 output schema, the description does a fair job of telling the agent what comes back (full body with templated placeholders). It omits error/not-found behavior and gives no hint about the required identifier, which is the main gap for a one-parameter getter.

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% and the single parameter script_id is undocumented in both schema and description. The description says nothing about where the id comes from (presumably list_scripts) or its format, so the agent gains no parameter meaning it did not already have.

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 and resource ('One teleprompter script in full') and scopes the visibility ('personal, or a team script the user can see'). It is clearly distinguishable from list_scripts, though it never names that sibling explicitly.

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?

Usage is implied rather than stated: an agent can infer this is the fetch-one counterpart to list_scripts, but there is no explicit 'use this when you have a script_id' or guidance on what to do if the script is not visible.

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