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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuine behavioral detail beyond that: newest-first ordering, the hard guarantee that archived submissions are never returned, and the spam-triage workflow. It stops short of describing result shape or pagination behavior, keeping it at 4 rather than 5.

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?

Three short sentences, front-loaded with the core verb and scope, then the default/alternate split, then the escalation hint. Every clause carries information an agent would otherwise have to guess.

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 read-only list tool with no output schema, the description covers what an agent needs to select it and set the key filters. The remaining gap is result-shape and pagination guidance, which is partly mitigated by the schema's limit documentation.

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%, so all five parameters including defaults and the 10/50 limit bounds are already documented. The description restates the spam flag semantics and the inbox default, which duplicates the schema rather than extending it, and says nothing about read, since, or limit. Baseline 3 is appropriate.

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 ('Lists recent submissions for a form') plus ordering ('newest first'), and immediately scopes which subsets it covers (inbox default, spam via flag, archived never). An agent can distinguish this from write-side siblings like bootform_delete_submissions or bootform_mark_submission without opening schemas.

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 names the default case (inbox), the alternate case (spam folder with spam: true), and the exclusion (archived never included). It also routes to a specific sibling with a concrete trigger condition: 'If the person says the form gets spam, or these look like spam, run bootform_check_spam first.'

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