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

Annotations already declare the safety profile (readOnly, non-destructive, non-idempotent, closed-world), so the bar is lower. The description adds real context beyond that: ordering ('newest first'), per-response payload contents, and an ownership/authorization constraint ('only works for forms the user owns').

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?

Front-loaded with the 'Use this when...' trigger, followed by ownership and return-format notes. Every sentence carries information, though the parenthetical example list is slightly expendable.

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 so return values needn't be detailed, yet the description still notes ordering and payload shape. Combined with annotations covering safety and the description's ownership constraint, an agent has everything needed to call it 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 coverage is 100% and the schema already explains the form parameter accepts a link or token. The description's 'Takes the form's link' adds only marginal clarity over the schema, which is the expected baseline-3 outcome when the schema does the heavy lifting.

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 (see/read) and resource (responses submitted to a shareable form) and explicitly ties itself to create_shared_form, making the relationship to siblings like create_shared_form, find_forms, and submit_form clear. The example list (sign-ups, survey answers, RSVPs, feedback) sharpens the domain.

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?

Gives a clear trigger ('when the user wants to see what people submitted') and a precondition ('forms the user owns'). It doesn't explicitly name a competing sibling (e.g. find_forms) or state when-not to use it, so it falls just short of full routing guidance.

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