export_employee_changes

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

With no annotations, the description alone must disclose behavioral traits. It mentions pagination but not the output format, what constitutes a 'change order', authentication requirements, or behavior for empty results. This is minimal and leaves significant ambiguity for a tool with no other context.

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 sentence that leads with the verb and resource, includes the key scope (date range) and a behavioral note (paginated), with no wasted words or repetition.

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 moderately simple export tool with well-described parameters, the one-sentence description is adequate but lacks details on output format, pagination mechanics, or a definition of 'change orders'. Given the absence of an output schema and annotations, more context would improve completeness.

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 100% descriptive coverage for all five parameters, so the baseline is 3. The description adds a little context by linking the date range and pagination to the parameters, but it does not offer additional per-parameter meaning beyond what the schema already states.

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 the specific verb 'Export' and identifies the resource as 'employee change orders', further constrained by 'within a date range' and 'paginated'. This clearly differentiates it from sibling tools like export_employees or export_organization_changes, which target different data.

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 a use case (exporting employee changes within a date range) but does not explicitly state when to use this tool over alternatives, nor does it mention exclusions. A clear context is present, but no alternatives are noted, so it falls short of a 4.

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