get_email_count

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

The description does not explain the effect of the optional 'name' parameter, whether it filters the count by email configuration, or what happens when the configuration does not exist. No annotations clarify behavior.

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 extremely concise and free of unnecessary words, 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?

The tool is simple and the description covers its main function, but it omits details about the optional parameter's filtering behavior and the exact return format. These gaps are notable but not severe given the simple nature of a count operation.

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 'name' parameter has a description indicating it is an optional email configuration name, but it does not explain how omitting it affects the count or whether the name must reference an existing configuration. Schema coverage is present but minimal.

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 returns the total count of emails, making its primary purpose unambiguous and distinct from sibling tools that return email lists or perform other operations.

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 given about when to use this tool instead of alternatives like get_all_emails or search_emails. The intended use case is only implied by the tool name.

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