access-shared-mailbox

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

The description confirms the read-only nature (consistent with annotation) and adds context: paged results, return shape identical to search-emails list mode, and the delegation requirement. No contradictions.

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 sentences, front-loaded with purpose, followed by essential details. No fluff.

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?

Given no output schema, the description outlines the return shape. It explains paging but omits continuation token details. Still, it covers core needs adequately.

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?

With 100% schema coverage, the description still adds value by explaining default values (folder=inbox, count=25, max 50), the role of outputVerbosity, and the email alias. It clarifies usage beyond schema but doesn't detail every parameter's exact format.

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 clearly states the tool lists emails from a shared mailbox (read-only). It specifies the resource and action, and distinguishes itself from siblings like 'search-emails' by noting the limited scope.

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 explicitly says when to use this tool (delegated shared mailbox) and when not to (prefer search-emails for full search/filter). Also mentions the prerequisite of admin-configured delegation.

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