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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine scope information beyond that: only metadata/approved fields are returned, and secrets, contacts, and original files are excluded, which tells the agent what it will not get back. It stops short of explaining pagination behavior despite limit/offset params.

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?

Two short sentences, front-loaded with the operation and immediately followed by the field-scope constraint. No filler, no repetition of the title.

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 helpfully characterizes the returned shape (metadata/approved fields only), which is the strongest part of the definition. But it is incomplete for a paginated search tool: pagination semantics and search behavior are absent, and the relationship to get_email_intake_submission is unaddressed.

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 0%, so the description carries the full burden, yet it mentions none of the three parameters. It gives no hint that 'query' performs a text search (max 150 chars), or that limit/offset paginate with defaults of 50/0 and caps of 100/25000 — all of which an agent needs to call this correctly.

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 ('Read') and resource ('email intake submissions') with a scope qualifier ('authorised'), so an agent knows this is a read/list operation over email intake records. It does not, however, distinguish itself from the closely-named sibling get_email_intake_submission, leaving the singular-vs-list distinction to be inferred from the name alone.

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?

There is no explicit when-to-use guidance, no mention of the singular get_email_intake_submission as the alternative for fetching one record, and no stated prerequisites beyond the implicit 'authorised'. The agent must infer list-vs-detail selection from the tool name.

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