get_postponed_submission_metadata

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

Annotations declare readOnlyHint=true, so the safety profile is already covered. The description adds real behavioral context the annotations cannot: output is streamed as newline-delimited JSON and capped at max_rows specifically to bound context size. It stops short of describing truncation/pagination interplay, but that lives in the max_rows schema description.

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 core action and stream format, then the differentiation. Slightly redundant: the 'postponed submission metadata only' point is made twice (paragraph two and the closing sentence), which is the only wasted space.

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?

Output schema and annotations exist, so return structure need not be explained. For a streaming, capped read tool the description supplies stream format, cap purpose and sibling routing — enough to call it correctly. Only the truncation/increment interaction is left implicit.

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%, so all three parameters are already documented, including max_rows default, truncation behavior and the increment cursor. The description only restates the max_rows cap, adding no syntax or format detail beyond the schema. 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+resource ('stream postponed submission metadata for a form') and immediately names the sibling it must not be confused with. The distinction from get_submission_metadata is spelled out, so an agent can differentiate without opening either 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?

Explicitly routes the agent: use this for postponed submissions only, get_submission_metadata for all submission metadata. That covers the primary selection decision, but there is no guidance on when postponed-only retrieval is preferable (e.g. follow-up workflows) or on the incremental-pagination parameter beyond what the schema says.

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