Export Attribute Rules

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

Annotations already indicate this is not read-only, not destructive, idempotent, and not open-world. The description adds useful behavioral context by stating that output goes inside EXPORT_ROOT and that existing files are not overwritten. It does not add auth or error details, but it meaningfully supplements the annotations.

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, compact sentence with two clear clauses. The export action and the overwrite constraint are front-loaded with 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?

With an output schema present, the description does not need to explain return values. For a simple two-parameter export tool whose annotations cover safety, the description provides enough context to understand the output destination and overwrite behavior. However, it remains incomplete regarding dataset_path semantics, which is a noticeable gap given 0% schema description coverage.

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%, so the description must compensate for two undocumented parameters. It gives output constraints that relate to output_csv, such as the EXPORT_ROOT location and refusal to overwrite, but it does not clarify dataset_path or describe the expected format of either parameter.

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 a specific verb and resource: exporting attribute rules as a new CSV. It also adds scope about the output location and overwrite behavior. However, it does not explicitly distinguish this tool from sibling tools like list, import, delete, or add attribute rules, so it falls short of a 5.

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 does not say when to use this tool versus alternatives such as list_attribute_rules, import_attribute_rules, or delete_attribute_rules. It only states what the tool does and includes a behavioral constraint about overwriting. No explicit usage context or exclusions are provided.

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