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

Annotations already declare readOnlyHint=true, so the description adds real context beyond them: filter combination is AND, results are paged via next_page, and the backing endpoint is GET /main/ChargeItemDefinition. It stops short of stating defaults or what a page response contains, but the safety profile is already covered 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?

Three short sentences: what it lists, how filters behave, how to page, plus the endpoint. Scope is front-loaded and no sentence is redundant.

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 the description should carry some return-shape burden; it names the paging mechanism (next_page) but not the response envelope or the default page size, which an agent must infer. Otherwise complete for a 10-parameter, all-optional read tool.

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%, so per-parameter meaning is already documented (baseline 3). The description adds cross-parameter semantics the schema cannot express — that filters are combined with AND — plus how pagination is driven by reusing next_page as page, which is genuine value beyond the field-level descriptions.

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 or search fees (ChargeItemDefinition)') and defines the domain object as 'the services and products a practice charges for', which an agent can immediately distinguish from halaxy_get_fee (single-fee retrieval) in the sibling list.

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?

'List or search' implies the two modes, and the pagination instruction gives procedural guidance, but it never states when to prefer this over halaxy_get_fee or when a search vs. a full listing is appropriate. Usage is implied rather than stated.

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