list_emails

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

Discloses ordering ('newest first') and pagination method ('cursor'), but does not discuss rate limits, authentication, scope of 'recent', or side effects. With no annotations, the description carries the burden and falls short of full transparency.

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?

Single sentence front-loads the main purpose (list recent emails) and quickly covers ordering, pagination, and optional filter. No wasted words.

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?

Lacks output schema or description of return format. For a listing tool, knowing the fields returned (e.g., id, subject, status) would enhance completeness. However, the tool's simple nature and sibling context (get_email) partially compensate.

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?

Input schema already describes all 3 parameters with good coverage (100%). Description adds value by explaining the 'newest first' ordering (implied by default) and clarifying that 'after' is a cursor for pagination, beyond schema descriptions.

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?

Clearly states the tool lists recent emails for a project, sorted newest first, with cursor pagination and optional status filter. Distinct from siblings like 'get_email' or 'get_analytics'.

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?

Describes optional filtering and ordering, but does not provide explicit guidance on when to use this tool vs alternatives (e.g., when to use 'get_email' instead). No when-not statements.

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