Get Severity

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered without the description. The description adds nothing behavioral beyond restating 'retrieves' and does not mention the UUID-or-slug lookup flexibility or the response shape (though an output schema exists, lowering the burden).

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 concise, front-loaded sentence with zero padding. It is efficient, though its brevity leaves the tool slightly under-explained rather than over-explained.

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 simple single-parameter getter with full schema coverage, annotations, and an output schema, the essentials are present. However, the description omits any hint about what a severity represents or how the ID is obtained, leaving a mild gap for an unfamiliar agent.

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 100% and the schema already explains that id accepts a UUID or a slug and warns against using a nonexistent severity_id argument. The description's 'by id' adds no meaning beyond the schema, so the baseline 3 is appropriate.

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 (retrieves) and resource (severity) scoped to a single record by id, which reads clearly as the get-by-id counterpart to list_severities. It does not explicitly name or differentiate against its siblings (list_severities, update_severity, create_severity), so it stops short of a 5.

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?

The description gives no when-to-use context, no mention of when to prefer list_severities versus fetching a single severity, and no prerequisites or exclusions. An agent must infer all routing from the tool name alone.

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