search_incidents

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

No annotations provided, so description must carry full disclosure. It explains pagination but omits critical behavioral traits: it's a read-only operation, no side effects, no rate limits or authorization hints. The output schema exists but description doesn't confirm that results are returned.

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?

Structured as a compact docstring with Args section. Every sentence is informative and necessary. No wasted words.

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?

Covers the core usage of all three parameters, defaults, and pagination. Output schema is present, so return details are provided structurally. Could mention that the tool returns a list of incidents matching the query.

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 0%, yet description adds rich meaning: query is a ServiceNow encoded string with examples, limit default 10, offset for pagination. This fully compensates for the lack of schema 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?

The description clearly states 'Search incidents using a ServiceNow encoded query' with a specific verb and resource. It distinguishes from sibling tools like get_incident (single record) and mutation tools.

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?

Describes when to use the encoded query, including examples and the behavior when query is empty. Provides pagination guidance via limit and offset. Lacks explicit contrast with siblings or exclusion scenarios.

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