servicenow_list_records

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

With no annotations, the description carries the full burden and does not state that this is a read-only operation, what pagination/default-limit behavior applies, whether displayValue affects output, or what permissions are needed. It adds nothing about destruction risk or result shape beyond 'list records'.

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?

A single front-loaded sentence with no filler; every clause maps to the tool's behavior. It is concise to the point of under-specification, but there is no structural waste.

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 5-parameter tool with no annotations, no output schema, and 0% schema description coverage, one sentence is not enough. An agent cannot determine query syntax, pagination, output format, or safety characteristics from the definition alone.

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 0% across 5 parameters, yet the description only alludes to 'query' and 'fields' and mentions the table conceptually. It does not explain encoded-query syntax, the limit/default of 10, max 100, or what displayValue toggles, leaving most parameters undocumented in both places.

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 (List) and resource (records from any ServiceNow table), and names the filtering mechanism (encoded query, field list). It is clearly distinguishable from the create/update/delete/get siblings, though it does not explicitly contrast itself with servicenow_get_record.

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?

There is no guidance on when to use this versus servicenow_get_record or any other sibling, no mention of prerequisites (auth, roles), and no note on when an encoded query is appropriate versus listing unfiltered. The word 'optional' on the query is the only usage hint.

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