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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds non-obvious behavior beyond that: results are ordered newest first, each entry carries answers plus a timestamp, and the call is restricted to forms the user owns (an authorization/ownership constraint not present in the schema).

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?

The triggering condition is front-loaded in the first sentence, followed by argument shape, return behavior, and the ownership constraint. No sentence is redundant and none could be dropped without losing routing or behavioral information.

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?

An output schema exists, yet the description still briefly characterizes the return (newest first, answers and time), which is more than required. Combined with the ownership restriction and the pointer to its sibling, an agent has everything needed to select and call this tool correctly.

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 100% for the single 'form' parameter, so the baseline is 3. The description adds meaning the schema does not: the parameter must be a form the user owns, and it restates the acceptable value shape (link or token) in user-facing terms.

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?

The description names a specific verb and resource (read responses submitted to a shareable form) and grounds it in concrete examples — sign-ups, survey answers, RSVPs, feedback. It also explicitly links the tool to the sibling that creates the resource (create_shared_form), so an agent can place it in a workflow without opening the schema.

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?

It gives a clear triggering condition ("Use this when the user wants to see what people submitted…") and names the originating sibling, create_shared_form. It stops short of naming an alternative or exclusion other than the ownership constraint, so it is strong but not a full when/when-not routing rule.

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