chaprola_export

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the export action but does not confirm whether the operation is read-only, whether it modifies or deletes the source files, or if authentication or special permissions are required. The term 'export' implies a non-destructive conversion, but this is left implicit.

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 that immediately conveys the tool's purpose. It avoids unnecessary detail and is well-structured for quick parsing by an AI agent.

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?

The tool has no output schema and no annotations, and the description does not explain what the tool returns (e.g., JSON content, file path, success status). For an export operation, the return value is a critical piece of information that is missing. The description covers the action and parameters but leaves the outcome ambiguous.

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 provides complete descriptions for both parameters (name and project), so schema coverage is 100%. The tool description adds no additional parameter semantics beyond what the schema already offers, which is acceptable given the high coverage.

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 the tool exports Chaprola .DA + .F files to JSON, using a specific verb and resource. It differentiates itself from siblings like chaprola_export_report and chaprola_download by specifying the exact file types and output format.

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 when to use the tool (when you need to convert .DA + .F files to JSON) but provides no explicit exclusions or alternatives. It does not mention when to prefer this over chaprola_export_report or chaprola_download, leaving the agent to infer the appropriate context.

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