drc_export_rules

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

The openWorldHint annotation already signals that the tool may interact with the external world, and 'Export... file' implies file-system side effects. However, the description does not disclose important behavior such as what happens when output_path is omitted, whether files are overwritten, or whether the tool returns file content.

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 with no wasted words. It efficiently conveys the action, resource, and intended use.

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?

Although the tool is simple and has an output schema, the description lacks essential contextual details about the optional output_path parameter and side-effect behavior. The presence of openWorldHint and an output schema does not make up for the missing parameter semantics and usage guidance.

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 does not mention output_path at all. With only one optional parameter, the agent is left to infer what the parameter means, what 'null' default does, and how the export destination is determined. The description fails to compensate for the schema's lack of parameter documentation.

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' with a clear resource 'the active custom DRC rules file' and purpose 'for sharing or CI.' This clearly distinguishes it from sibling tools like drc_list_rules, drc_rule_create, or run_drc.

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 phrase 'for sharing or CI' gives some context for when to use the tool, but there is no explicit guidance about when to choose this over related tools such as drc_list_rules or other export_* tools. No exclusions or alternative recommendations are provided.

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