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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description contributes nothing beyond that — no indication of scope, volume, pagination, or what an incident record contains — but it does not contradict the annotations either.

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?

It is short, but the brevity is under-specification rather than economy — only six words exist, and none of them are front-loaded actionable information. There is no wasted text, but there is also almost no text to evaluate.

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?

With no output schema and a bare-bones input schema, the description is the only place return shape and usage context could be conveyed, and it conveys neither. An agent cannot determine what this call produces or when it applies.

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 0% for the single required parameter system_id, so the description must explain whether this is a system identifier, which namespace it belongs to, or what format it takes. It says nothing, leaving the parameter's semantics inferable only from its name.

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?

"[security] Incident registry" is a noun phrase that essentially restates the tool name and title, with only a category tag added. It never states a verb (list, fetch, query) or what the registry returns, and it does not distinguish itself from the very similar sibling compliance_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?

There is no guidance on when to use this tool versus alternatives. With siblings like compliance_incident, compliance_check and compliance_explain in the toolset, an agent has no basis for choosing among them from this description.

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