get_service_incident

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

Describes the output content (full detail with timeline). Given no annotations, it sufficiently discloses behavior for a read-only get operation, though it does not explicitly state it is read-only.

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 tight sentences. First sentence states purpose and output, second gives prerequisite. Action verb 'Get' is front-loaded. No unnecessary 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 purpose, output content, and prerequisite. Output schema exists, so return values need not be detailed. However, it does not differentiate from sibling 'get_incident' or explain the 'slug' parameter.

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?

The description adds meaning for 'incident_id' by referencing its source but does not explain 'slug'. With 0% schema description coverage, it only partially compensates.

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 specifies the action 'Get', the resource 'one vendor incident', and details the included timeline. It distinguishes from sibling 'list_service_incidents' by noting that IDs come from there.

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?

Provides clear prerequisite: 'Get incident IDs from list_service_incidents.' However, it does not contrast with sibling 'get_incident' or specify when to use this tool over alternatives.

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