export_education_history

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Export all employees' education records,' which implies a read-only retrieval but does not explain output format, pagination, authentication requirements, or lack of side effects. The minimal wording leaves the agent to infer expected behavior.

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 redundant words. Every word contributes to understanding the tool's purpose. It is appropriately front-loaded and easy to parse.

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?

For a zero-parameter export tool, the description covers the core function but leaves out context about the output format (e.g., file type), whether it modifies anything, and any caveats. With no annotations or output schema, the description is the sole source; while it's enough for a simple export, it could detail the return style.

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 tool has zero parameters, so the schema is trivially complete. The description adds semantic meaning by clarifying the scope ('all employees'), which acts as a built-in filter. Even though no parameters need explanation, the description successfully conveys what data will be returned.

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 action (export), the resource (education records), and the scope (all employees). This distinguishes it from sibling export tools like export_working_history or export_employees, which target different data categories.

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 the tool is used when you need education records for all employees, but it does not explicitly state when to use it versus alternative tools or provide exclusions. Since there are many export siblings, a brief note on when this is preferred would improve guidance.

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