servicenow_get_incident

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

No annotations provided, so description must cover behavioral traits. It does not disclose authentication needs, error handling (e.g., incident not found), or return format. The phrase 'full details' is vague. More context is needed for safe invocation.

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?

Single sentence, front-loaded with action and resource. However, important information is missing, making it under-specified rather than optimally concise.

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?

Given no output schema, no annotations, and a parameter mismatch, the description is incomplete. The agent lacks details on how to invoke the tool correctly (missing required inputs) and what to expect in return.

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?

Input schema has no properties, yet description implies parameters (number or sys_id). This mismatch reduces clarity. Description adds meaning beyond the empty schema, but the lack of formal parameters limits usefulness and may confuse the agent.

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 the tool retrieves full details of a specific ServiceNow incident by number or sys_id. It distinguishes from sibling tools like servicenow_search_incidents and servicenow_list_my_incidents. However, the input schema has no parameters, creating ambiguity about how to specify the incident.

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 guidance on when to use this tool versus siblings. Does not mention prerequisites (e.g., must connect to ServiceNow first), exclusions, or context for use. The description only states what the tool does, not when to use it.

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