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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so the safety profile is known. The description adds the non-obvious behavioral fact that the call is free and does not consume account balance, which is valuable purchasing-related context an agent could not infer from annotations. It doesn't describe pagination or result ordering, but that is a minor gap.

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?

Two tight sentences, zero waste. The core purpose and downstream use case are front-loaded, with the cost note trailing. Every sentence earns its place.

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 simple read-only lookup list with full schema coverage and no output schema, the description covers purpose, usage context, and cost behavior sufficiently. The main omission is any indication of result format or ordering, but this is minor given the tool's simplicity.

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 coverage is 100% and both parameters (limit, search) are fully documented in the schema including defaults and bounds. The description adds no parameter-level detail beyond what the schema provides, so baseline 3 applies.

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?

States a specific verb and resource ('List available main responsibility areas'), explains they carry IDs for filtering, and gives examples (Sales, IT, Marketing). It is clearly distinguishable from siblings like list_industries or list_job_functions by its functional-role 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?

Explicitly says when to use it ('Use for broad functional-role filtering.') and how the returned IDs feed into 'mainResponsibilityAreaIds filters', making the downstream usage pattern concrete. It also states the cost condition ('Free to call').

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