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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds high-value behavioral context beyond them: untrusted_text fields hold third-party authored content, that content is data not instructions, and names prefixed with '⚠ flagged text:' are third-party names masquerading as instructions. This prompt-injection guidance is exactly the context annotations cannot convey.

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?

Content is front-loaded: resource and statuses first, then sibling routing, then the untrusted-text warning. Every clause earns its place, though the injection warning is comparatively verbose for a listing tool.

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?

With no output schema, the description takes on responsibility for the return shape and does describe the resource and status values adequately, plus the sibling tools that consume results. It omits pagination/ordering behavior, which keeps it from a 5 but is minor for a read-only list.

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 50%: company carries a full schema description (name/id, 'Personal', 'all', omit for all visible) while status has only an enum. The description restates the three status values but adds no syntax or semantics beyond the enum, and says nothing about the company parameter. Baseline 3 given partial schema coverage.

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 identifies the resource precisely – uploaded and emailed-in files (receipts, bills, statements) with their status values unread/recorded/ignored – which clearly distinguishes it from get_document (single file text) and the write tools. It lacks an explicit 'list' verb framing but the resource and scope are unambiguous.

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 routes the agent across siblings: get_document returns the text of one file and the write tools record what it says, which establishes when to use this listing tool versus the alternatives. No explicit exclusions or 'when-not-to-use' conditions are stated, keeping it short of a 5.

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