export_contacts

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

Annotations indicate destructiveHint=true, so the description's mention of initiating an export is consistent. However, it does not elaborate on what 'destructive' entails (e.g., whether it overwrites previous exports or triggers a download). The optional email sending is a helpful behavioral detail.

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 two short sentences, front-loading the primary action and mentioning the optional parameter. No unnecessary 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 tool initiates an export (with destructiveHint true) and has no output schema, the description should clarify whether the export is asynchronous, where the file goes, or how to retrieve it. The current description leaves important context gaps.

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 only parameter, email_urls, is described as optional recipients for the exported file. This adds meaning beyond the schema (which only specifies type and format), but lacks details like whether multiple emails are allowed or any constraints.

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 that the tool initiates an export of all contacts and optionally sends the exported file to specified emails. This is specific and unambiguous, especially since no sibling tool performs an export.

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?

The description explains what the tool does but provides no guidance on when to use it versus alternatives or any prerequisites. It does not mention if this is an asynchronous process or any limitations.

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