read_inbox

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

No annotations are provided, so the description carries the full burden, yet it only supplies the bracketed "read-only" tag. It says nothing about whose inbox, how many messages are returned, ordering, or pagination behavior — important for an unbounded-looking list operation.

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?

Very short and front-loaded, which is good, but the bracketed "passed through by intentplane" is implementation noise that consumes a third of the text without informing the caller. Brevity here reflects under-specification more than discipline.

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-value shape needn't be explained, but the description still omits scope (which account/inbox), result-size behavior, and ordering for a read-list tool with no annotations to fall back on. Too thin for an agent to call with confidence.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline of 4 applies. The schema is empty and fully consistent with the described behavior.

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 emails in the inbox" identifies the resource but not the operation — it reads as a noun phrase rather than stating that the tool returns/reads messages. The read-vs-send distinction against the send_email sibling is only weakly implied.

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?

No guidance on when to call this versus siblings; an agent must infer that this is the read counterpart of send_email. No mention of prerequisites, scope, or result limits that would inform the choice.

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