Computers with a licensed software

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that each computer's corresponding license is included in the result, which is useful behavioral context beyond basic read-only. It does not disclose pagination or filtering specifics, but those are in the schema.

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, concise sentence that conveys the core functionality and a key detail (license mapping). No unnecessary words or repetition.

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?

The tool has six parameters and no output schema, but the description plus annotations and schema adequately cover the operation. It clearly states the primary purpose and the license mapping detail, while pagination and filter behaviors are already documented in the schema. Sibling tools provide additional context for differentiation.

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 all six parameters already have descriptions. The description references licSwId's source (inventory_license_software_list), but the schema already provides this, so no additional meaning is added. The mention of license mapping hints at licenseFilter but not explicitly.

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 the tool retrieves computers for a specific licensed software, using a specific verb ('Retrieves') and resource. It also mentions the inclusion of license mapping, which distinguishes it from sibling tools like inventory_computers_by_software and inventory_computers_by_license.

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 indicates the required parameter comes from inventory_license_software_list, providing clear context on the input source. However, it does not explicitly mention when to avoid this tool or name alternative sibling tools, so it lacks explicit exclusions.

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