List installed software for an endpoint

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the tool's safety profile is clear. The description adds little behavioral context beyond what annotations provide—no mention of pagination behavior, rate limits, or response size considerations.

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 a single sentence (12 words) that is front-loaded with the action and scope. Every word earns its place, with no redundancy or fluff.

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 6 parameters (including pagination and output format) and a detailed output schema, the description is brief. It doesn't explain pagination mechanics or the default output format. Given the tool's complexity, more guidance would be helpful, but the schema and annotations fill many gaps.

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%, so the schema already documents all parameters. The description adds value by clarifying the 'find_by_name' parameter as a 'substring filter', but it does not provide additional meaning beyond the schema for other parameters like cursor, limit, or response_format. 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?

The description clearly states it fetches installed-software inventory for one endpoint with an optional name substring filter. It uses specific verb and resource, differentiating from sibling tools like 'action1_list_installed_software_data' or 'action1_requery_installed_software_for_endpoint'.

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 says 'for one endpoint' and mentions the optional filter, which provides some context, but it does not specify when to use this tool versus alternatives (e.g., list_installed_software_data or requery). No explicit when-not-to-use or alternative guidance is given.

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