Show Witness Statement

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

Annotations already indicate readOnlyHint true and destructiveHint false. The description adds that it returns a JSON object, which is consistent but does not disclose additional behavioral traits beyond what annotations provide. No contradictions.

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?

The description is concise with 4 sentences, but includes a typo ('Incidents') and technical endpoint details that may not be essential for an AI agent. Still, it is not bloated and fairly efficient.

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?

The description covers required parameters but omits explanation of optional parameters (incident_id, page, per_page) and their effect. It also confuses 'Incidents' with 'Witness Statement'. For a single resource fetch, it is partially complete but has gaps.

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 100%, so parameters are already documented. The description only mentions required parameters (project_id, id) and the endpoint structure, adding no significant meaning beyond the schema.

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 it returns the specified Witness Statement and fetches full details. It distinguishes from siblings like list_witness_statements (which lists all) and create/update/destroy.

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?

It says 'Use this to fetch the full details of a specific Incidents by its identifier,' but does not explicitly exclude alternatives or mention when not to use. It implies usage for single retrieval but lacks explicit guidance against using list or other tools.

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