Get mailbox quota

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

No annotations are provided, so the description carries the behavioral transparency burden. It discloses the return data (storage limit, usage, email count) but does not explicitly confirm the operation is read-only or mention potential errors or permissions. This is sufficient for a simple getter but lacks depth.

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?

The description is a single concise sentence that adequately conveys the tool's purpose and result. It is front-loaded with the key action and includes necessary specifics without 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?

The tool is simple with one parameter and no output schema. The description explains what the tool does and the data it returns, providing enough context for an agent to understand the operation. However, it doesn't specify the response structure or field names, which would be useful without an output schema.

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 only parameter 'address' is fully described in the schema as 'The full mailbox address'. The description adds no extra meaning beyond the schema, so with 100% schema coverage, a baseline score of 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?

The description clearly states the tool's function with a specific verb ('Get') and resource ('mailbox quota'), and enumerates the specific values returned (storage limit, usage, email count). This distinguishes it from sibling tools like get_mailbox_stats and update_mailbox_quota.

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?

The description implies the tool is for retrieving quota information but does not explicitly contrast it with sibling tools like get_mailbox_stats or update_mailbox_quota. There is no explicit guidance on when to use this over alternatives.

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