export_data

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

No annotations available. Description does not disclose side effects (e.g., file overwrite), authentication needs, rate limits, or output behavior. For a write operation, this is a significant gap.

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?

Single sentence, no redundancy. Could be more structured (e.g., list key points) but adequate for a simple export function.

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?

Missing context on export behavior (server-side save vs download), output format details, compression effect, and selection expression. Incomplete for a 7-parameter tool with no output schema.

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 coverage is 71% (5/7 params described). Description adds no extra meaning beyond schema; it only lists formats already in enum. Baseline 3 appropriate as schema handles most parameter understanding.

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?

Description clearly states action (export branch data) and formats (JSON, CSV, Parquet). It distinguishes from siblings like read_branches (reading vs export) but does not explicitly contrast with get_branch_stats or validate_file.

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?

No guidance on when to use export_data vs alternatives (e.g., read_branches). No prerequisites, limitations, or suggested scenarios provided.

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