acedatacloud_export_orders

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions the output is 'bounded CSV text' and scoped to 'caller orders', but does not explain what happens when the bound is exceeded (e.g., truncation, error), whether authentication is required, or any side effects. The behavioral picture is incomplete.

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, concise sentence with no wasted words. It front-loads the action ('Export') and includes key qualifiers ('caller orders', 'bounded CSV text') that add value without redundancy.

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's simplicity, the existence of an output schema, and fully described parameters, the one-line description provides the core purpose. However, it lacks usage context (e.g., when to choose this over list_orders) and details about bounded behavior, leaving some completeness gaps. It is minimally viable but not comprehensive.

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 input schema has 100% description coverage for all five parameters, so the schema already handles parameter meaning. The tool description adds no additional parameter semantics, but the baseline is 3 when schema coverage is high.

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 uses a specific verb ('Export'), identifies the resource ('caller orders'), and specifies the output format ('bounded CSV text'). This clearly distinguishes it from sibling tools like list_orders (which likely returns structured data) and export_usage (which exports a different resource).

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 word 'Export' implies a file-download use case, and 'bounded CSV text' hints at size-limited exports. However, the description does not explicitly state when to use this tool over alternatives like list_orders, nor does it mention any exclusions or prerequisites. It relies on implied usage rather than explicit guidance.

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