list_org_units

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

Annotations indicate readOnlyHint=true and destructiveHint=false, so the description's 'Retrieve' aligns. It adds important behavioral details beyond annotations: default single-page return, auto-pagination with all:true, and format options. No contradictions with annotations.

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 concise at three sentences, with the main purpose front-loaded. Every sentence adds essential information (default behavior, auto-pagination, format option), and there is no wasted text.

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 7 parameters and no output schema, the description covers key usage points: pagination control, filtering via select, and output format. It lacks detail on sortBy/sortOrder and the exact return structure, but these are adequately described in the schema. Overall, it provides sufficient context for correct invocation.

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 100%, baseline 3. The description adds value by explaining the all parameter's effect on pagination, the format parameter's CSV use case, and the select parameter's filtering behavior with an example. This enhances understanding beyond the schema.

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 retrieves a list of all organization units. It distinguishes from sibling tools like list_org_unit_children by focusing on the full list, and the parameter details further clarify its scope.

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 provides guidance on pagination and output format (csv vs json), which helps in parameter selection. However, it does not explicitly state when to use this tool over other list tools (e.g., list_org_unit_children), leaving the agent to infer based on the tool name.

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