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

Annotations already declare it is a non-read-only, non-idempotent, open-world write, so the safety profile is covered. The description adds no behavioral context beyond that: it does not say unknown/unlisted fields are accepted, what validation or error behavior looks like, or that entity/permission scoping applies (assets are created into an entity).

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?

Two sentences, purpose front-loaded, no filler. The trailing field enumeration is a dense list rather than prose, which is efficient, though it reads more like a schema restatement than curated guidance.

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 not be described. However, for a create operation with a fully open nested payload, the description omits whether additional fields beyond the 'common' list are accepted, whether name is required, and any permission/entity prerequisite — the agent lacks what it needs to invoke this reliably beyond a bare happy path.

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?

Top-level schema coverage is nominally 100%, so the baseline is 3, but the nested 'input' object is `additionalProperties: {}` with only 'Asset fields' as its description. The field list (name, entities_id, serial, locations_id, states_id, ...) is the only real guidance for that open object, which adds value, yet it is flagged as merely 'common' with no indication of which fields are mandatory or how they vary by asset_type.

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?

States a specific verb and resource ('Create an asset'), and the asset domain is distinguishable from the many sibling create_* tools (ticket, user, document, entity). It stops short of naming what an 'asset' covers versus those siblings, but the intent is unambiguous.

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?

There is no when-to-use guidance, no prerequisites (e.g. required permissions or referenced entity/user IDs needing to exist first), and no pointer to glpi_get_asset / glpi_list_assets / glpi_update_asset as related siblings. The agent must infer all of this.

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