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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the useful detail that results come back one page at a time and cites the REST path, but says nothing about ordering, page-size defaults, or what happens when filters match nothing.

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 short clauses with no filler, and the pagination constraint leads. The endpoint reference is arguably redundant given the tool name but is cheap and unambiguous.

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 7-parameter filtered list tool with no output schema, the description never states what a record contains or how filtering and field selection interact. The rich schema compensates for most parameter gaps, but the description leaves the agent guessing about return contents and ordering.

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%, so limit, pageIndex, fields, wField/wValue and wOperator are already documented in the schema. The description's only contribution is the pagination framing ('one page'), which is already implied by pageIndex; 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?

The description says only 'Read one page of related records' — it never names notes or accounts, so the purpose is carried almost entirely by the tool name and title. It does convey the read-many/paginated shape and the underlying endpoint, which distinguishes it from the singular get_note, but only weakly.

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?

No statement of when to use this versus servicemonster_list_notes, servicemonster_get_note, or servicemonster_list_order_notes. The only implicit guidance is 'one page', which hints at pagination but not at tool selection or prerequisites (e.g. needing a valid account id from a preceding read).

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