archery_export_query

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

No annotations are present, so the description bears full responsibility. It discloses key behavioral traits: read-only nature, batched export, default page size of 5000, and no limit on total rows. This goes beyond the schema by clarifying execution semantics. However, it does not mention how output is delivered (e.g., file path vs. content) or any permission requirements.

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 a single, front-loaded sentence. Every phrase adds value: read-only, export CSV, batching, default page size, and total row limit. 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?

Given the presence of an output schema, the description does not need to spell out return values. It adequately covers the core behavioral aspects: batching, page size, unbounded rows. But it lacks information about how the CSV is returned or prerequisites like instance configuration, which are not covered elsewhere.

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 description coverage is 0%, and the description adds minimal parameter meaning. It mentions page_size default and max_rows behavior ('默认每页 5000 行，不限制总行数'), but does not explain instance_name, database, sql, schema, or filename. Most parameter meanings (like instance_name) are not obvious, leaving the agent to guess.

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 '将只读查询分批导出为 CSV' clearly states a specific verb (exporter), resource (read-only query), and output format (CSV) with a batching mechanism. It distinguishes from siblings like 'archery_query' which presumably returns raw results rather than exporting to CSV.

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 implies usage for read-only queries that need CSV export in batches, providing clear context but no explicit exclusion or alternative tool reference. It does not explicitly say 'use this instead of archery_query when...' but the purpose is transparent enough to infer selection.

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