RiverScript

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds the meaningful scope constraint that only publicly shared transcripts are reachable and that translations are included. It says nothing about failure modes such as invalid, revoked or private links, and nothing about size or truncation limits.

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 sentences, no filler, with the identity of the resource front-loaded and the usage trigger immediately after. Every clause carries information the agent needs.

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 rich annotations and no output schema, the description covers purpose, trigger and the usable outputs of the fetched text. The only real gap is what the agent should expect when a link is dead or private.

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% and the single parameter is fully described there, including the example URL and the bare-token alternative. The description only restates 'given its share link' and adds no syntax or format meaning beyond the schema, so the baseline 3 applies.

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 — fetching the full text of a publicly shared RiverScript transcript — and scopes it to a share link. The added note that it works for both transcripts and translations makes the resource boundary explicit. No siblings exist, so no differentiation is owed.

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?

Names the trigger condition concretely: the user pastes a riverscript.com/share/... link or asks about its contents. It also enumerates the downstream tasks the fetched text supports (answer questions, summarise, quote, translate), removing ambiguity about when this tool is the right call.

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