get_license_status

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds genuinely new behavioral context: 'truncated' is always False (complete inventory), license keys are never returned, and 'assignments' is null with a note when the account lacks read permission. It also flags that assigning a license is a write, which the read-only annotations would not convey.

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?

Front-loaded with the one-line purpose, then return shape, then usage. Information-dense and mostly waste-free, though it runs long across several sentences and the assignments/expiry explanation could be tightened.

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 carries the full burden of describing returns and does so thoroughly (row fields, envelope, unlimited flag semantics, assignments behavior). An agent has everything needed to interpret results correctly.

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?

Single optional 'target' parameter with 100% schema description coverage, so the schema already documents it. The description never mentions 'target' or its default-to-config behavior, adding no meaning beyond the schema — baseline 3 applies.

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?

Opens with a specific verb+resource+scope: '[READ] vCenter/ESXi license inventory with usage and expiry.' An agent can distinguish this from sibling read tools immediately, and the field list (edition_key, total/used units, expiration) further nails down the resource.

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 names the use case ('catch over-allocation or an approaching expiry') and positions itself in a platform-hygiene sweep alongside get_certificate_status and get_ntp_status. No when-not-to-use or exclusion guidance, which is the only gap.

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