List Departments

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

Beyond the annotations (readOnlyHint=true, destructiveHint=false), the description adds valuable behavioral details: the response is a paginated JSON array with pagination metadata, and page/per_page control pagination. It also mentions the endpoint. This provides additional context not captured by 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, with three sentences that front-load the main purpose and essential details. Every sentence adds value: purpose, usage guidance, pagination behavior, required parameter, API reference. No fluff.

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?

Given the simplicity of the tool (3 straightforward params, no output schema), the description covers the essential aspects: purpose, pagination, required parameter, and return format. Mentioning the pagination metadata compensates for the lack of output schema. The endpoint reference adds helpful context.

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 already fully describes all three parameters (100% coverage). The description reiterates the use of page and per_page for pagination and the requirement of company_id, but adds little new semantic meaning beyond what the schema provides. 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 returns a list of Departments, specifies it enumerates Directory records, and gives concrete use cases: paginated overview, finding IDs, filtering. The verb 'list' matches the resource, and the description distinguishes it from siblings by explicitly mentioning 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 explicit guidance on when to use this tool ('when you need a paginated overview, to find IDs, or to filter by query parameters'). It also notes the required parameter company_id. Although it doesn't explicitly state when not to use it or provide alternatives, the context is clear.

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