smartlead_get_mailbox_count

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves a count, implying a read-only operation, but doesn't mention performance aspects like rate limits, authentication requirements, or whether the count is real-time or cached. This leaves significant gaps for a tool in a context with many sibling operations.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 the tool's simplicity (0 parameters, no output schema) and the lack of annotations, the description adequately covers the basic purpose. However, in a complex server with many sibling tools, it could benefit from more context on how this count integrates with other mailbox-related operations or spam testing workflows.

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 has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter details, but this is appropriate as there are no parameters to explain, aligning with the baseline for zero-parameter tools.

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 action ('Get the count') and resource ('all mailboxes used for any spam test'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'smartlead_get_mailbox_summary' or 'smartlead_get_campaign_mailbox_statistics', which might offer overlapping or related mailbox information.

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 is provided on when to use this tool versus alternatives. The description mentions 'spam test' context, but it doesn't specify prerequisites, exclusions, or compare it to sibling tools that might handle mailbox data differently, leaving the agent without clear usage context.

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