discover_email_folders

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

No annotations provided. Description mentions connection to IMAP but does not state whether the operation is read-only or if it modifies anything. For a discovery tool, read-only behavior is likely but not confirmed, leaving ambiguity.

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 conveying the core function efficiently. The inclusion of [query] is slightly unclear but does not detract significantly. No superfluous 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?

Given the simplicity (one param, no output schema, no annotations), the description covers the tool's purpose but fails to describe the return value format or any prerequisites. The [query] placeholder adds confusion.

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 one parameter 'id'. Description aligns with schema (ID of email account) but does not add new information beyond what the schema's description already provides.

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 discovers IMAP folders by connecting to an email account's IMAP server. It specifically mentions standard folders (Sent, Trash, Archive, Spam) and automatic detection, distinguishing it from tools like update_email_folders.

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?

Implies use after an email account is set up, but lacks explicit guidance on when to use vs. alternatives like update_email_folders or get_email_accounts. No prerequisites or exclusions provided.

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