get_system_updates

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

No annotations provided, so description carries full burden. It reveals that by default CVEs are omitted for lower token usage, that it returns a compact update list with counts and meta, and that `system_identifier` can be name or ID. Could mention if any side effects or permissions needed, but as a read operation this is sufficient.

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?

Multiple sentences but each provides useful information. Front-loaded with purpose. Could trim phrasing, but no redundancy. Efficient overall.

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?

Given the simple parameter and existence of output schema (though not shown), the description covers what the tool returns, default behavior, alternatives, and input handling. No gaps for an agent to correctly select and invoke this tool.

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?

Input schema has 1 parameter with 0% coverage. Description adds meaning by clarifying that `system_identifier` accepts either system name or system ID, with preference for ID, and explains the fallback. This compensates well for the bare 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?

Description clearly states 'Get pending updates for one system' (verb + resource). It distinguishes from sibling `query_system_updates` by noting this is for a compact default view, while the sibling handles pagination and CVE expansion.

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?

Explicitly advises when to use this tool ('Best for compact default update view') and when to use alternatives ('For pagination and CVE expansion, use query_system_updates'). Also provides resolution path for name not found via `find_systems_by_name`, and recommends preferring `system_id` over `system_name`.

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