list_drivers

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

No annotations are provided, so the description must disclose behavior. It states it returns drivers sorted newest first and lists filter effects, but does not mention permissions, read-only nature, or behavior when no results. Adequate but lacking detail.

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: a header sentence, a bullet-style parameter list, and a brief usage tip. It is front-loaded and every sentence adds value with no waste.

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 an output schema present (not shown), return values are covered. The description covers all 5 parameters and their defaults. Could add a note about typical use cases, but overall complete for a list 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?

Schema description coverage is 0%, so the description fully compensates by explaining each parameter: name_filter (substring match on name/provider), device_class (substring on class), third_party_only (exclude Microsoft), unsigned_only (only unsigned), max_items (max rows). This adds substantial meaning.

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 'Installed drivers with versions and dates, newest first,' specifying the resource (drivers), properties (versions, dates), and ordering. This distinguishes it from sibling tools like list_processes or get_system_overview.

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 provides filter options but does not explicitly state when to use this tool versus alternatives. The tip about investigating old or unsigned drivers near bug checks is helpful but not a clear usage guideline.

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