export_crm_contacts

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

With no annotations, the description must disclose behavioral traits, but it only says 'export as CSV'. It does not state whether the export is non-destructive, how the file is returned (e.g., download link, direct data), or if there are limitations on data volume. This lack of transparency could lead to incorrect invocation.

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 concise (one line), but the inclusion of '[query]' at the end is unclear and may confuse the agent. It could be more structured by separating purpose from usage hints. It earns its place but lacks clarity.

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 no output schema, the description should explain the output format and delivery method. It only says 'as CSV file' without specifying how the agent receives it (e.g., data URL, file path). Also, with many similar sibling tools, it lacks context to differentiate. The description feels incomplete for a data export 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 schema covers both parameters with descriptions (100% coverage). The description does not add new meaning beyond the schema; it merely repeats the filtering intent. Baseline score 3 is appropriate as schema does the heavy lifting.

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 states the verb 'export', resource 'CRM contacts', and format 'CSV file'. It clearly indicates the tool's purpose. However, it does not differentiate from sibling export tools like 'gdpr_export_customer_data' or 'export_conversations', which could cause confusion. A slight deduction for lack of sibling distinction.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, when not to use, or which specific context this export is for. The agent must infer solely from the name and purpose, which is insufficient.

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