export_organization_changes

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It mentions pagination, which is a useful behavioral trait, but it does not explicitly state whether the operation is read-only, what the output format is, or any side effects. This leaves significant behavioral uncertainty.

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 is front-loaded with the verb 'Export' and the resource, and it includes the key qualifiers 'within a date range' and 'paginated'. Every word adds value, with no redundancy or filler.

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 no output schema and no annotations, the description should provide more context about the return value, the meaning of 'change orders', and how pagination is handled. The presence of many sibling export tools increases ambiguity, and the one-sentence description does not fully clarify when this tool is the right choice.

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 full (100%) descriptions for all 5 parameters, including date formats and pagination defaults, so the schema does the heavy lifting. The description adds no additional parameter semantics beyond mentioning the date range and pagination, which are already covered in the schema. Baseline 3 is appropriate.

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 tool exports organization change orders within a date range, giving a specific verb and resource. However, it does not explicitly differentiate from similar sibling tools like export_employee_changes or export_organization_full, so it doesn't fully achieve the highest clarity score.

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 for exporting organization change orders filtered by date range, but it does not state when to prefer this over alternatives or provide exclusions. No alternative tools are mentioned, so the usage guidance is only implied.

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