get_mailbox

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

No annotations provided, so description carries full burden. States it retrieves mailbox info and lists fields, but does not mention permissions, side effects (none expected), or error behavior beyond the ambiguity note in schema. Adequate but not rich.

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 sentences, front-loaded with action and fields, no wasted words. Efficiently conveys purpose and usage.

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, description lists returned fields but not their types or structure. Includes some metadata (default/readiness, footer-policy). Missing error handling details beyond schema note. Adequate for a simple retrieval tool but not fully complete.

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 100% with descriptions for both parameters. The mailbox parameter description in schema is detailed (when to omit, ambiguity error). Description does not add significant meaning beyond schema; it only lists returned fields. Baseline 3.

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?

Clear verb 'Get' with specific resource 'mailbox info' and listed fields (ID, address, slug, default/readiness metadata, footer-policy). Distinguishes from siblings like list_mailboxes (which lists all) or create_mailbox (which creates).

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?

Explicitly states 'Use to check if a mailbox exists.' The parameter description for 'mailbox' also clarifies when to omit it (single mailbox project). Does not explicitly exclude alternatives or state when not to use, but provides sufficient context.

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