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

Annotations already declare readOnlyHint and openWorldHint, but the description adds genuinely new behavioral context: the list is curated and incomplete, so a zero-result must not be read as 'safe'. That caveat materially changes how an agent should report results. Missing only secondary details such as data freshness or rate limits.

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?

Four short sentences, front-loaded with what the tool returns, then usage, then the coverage caveat. Each sentence carries information, though 'with what to do and a link to the source' and the title overlap slightly in framing.

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, the description correctly compensates by describing the shape of returned entries (incident, remediation, source link). For a single optional-parameter read tool this is nearly complete; the only gap is not characterizing how current or how large the curated list is.

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% and the name parameter is already documented with an example, so baseline would be 3. The description goes beyond the schema by specifying the semantics of omission ('Omit name to list all'), which the schema does not state.

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 (lists) and resource (known security incidents at hosting, deployment and AI platforms), plus what each entry contains. The platform-vs-package boundary with siblings check_package/check_packages is only implicit through the word 'platform', so it is clear but not explicitly differentiated.

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?

'Use when the user asks about a platform or breach' gives a clear trigger, and 'Omit name to list all' explains the no-argument mode. It stops short of naming when to prefer check_package/check_packages instead, so an agent must infer the platform-vs-package split from the sibling names.

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