license_seats

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

Annotations already declare idempotent=true, destructiveHint=false, and readOnlyHint=false, so safety is covered. The description adds non-obvious behavior: checkout's one-target cardinality and the fact that checkin removes an assignment without deleting the licence or seat. It stops short of covering the non-seat parameters.

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?

Three short sentences with the action list front-loaded and the destructive-behavior caveat immediately after. No padding, though the structure is dense enough that the mutation caveat could be easier to scan.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. Still, for a mutating multi-action tool with seven undocumented parameters and no enum on the required action_name, the description leaves an agent guessing about pagination and note/ID semantics.

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 coverage is 0% with 8 parameters, so the description must carry the load. It usefully documents the valid action_name values and the assigned_user_id/assigned_asset_id exclusivity, but says nothing about limit, offset, seat_id, license_id, or note.

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?

Names specific verbs (list, checkout, checkin, update) against a specific resource (licence seats), and the seat-level scope distinguishes it conceptually from licences_search and licenses_write. It never names a sibling explicitly, so it falls short of full differentiation.

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?

"Use mutation actions only for explicit assignment requests" is a genuine when-to-use condition, and "checkout accepts exactly one user or asset target" scopes the mutation path. It gives clear context but does not point to alternative siblings (e.g. licenses_search) for read access.

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