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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds nothing beyond that — no indication of what a 'history' payload contains, whether it is paginated or versioned, or any retention/ordering behavior. The describe_operation pointer is the sole added value.

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?

It is short, but the same sentence is repeated twice, wasting the only content budget it has. Nothing is front-loaded beyond the raw endpoint, and the useful pointer to describe_operation is buried after the duplication.

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?

For a read tool with a nested free-form query object at 0% schema coverage and no output schema, the description should explain the query surface and what history records are returned. It leaves both undocumented, so an agent cannot call it correctly without a separate describe_operation round-trip.

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 0%, so the description carries the full burden, yet it says nothing about the required 'id' path parameter (format, valid identifier type) or the free-form 'query' object (supported filters, pagination keys). The ':id' placeholder in the REST path is the only implicit mapping, leaving the nested query parameter entirely undocumented.

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 is a raw REST path 'GET /api/asset-groups/:id/history' duplicated verbatim, which largely restates the tool name and title. It does imply the resource (asset group history) and the id-scoped nature, but provides no plain-language statement of what the tool returns or how it differs from sibling get_asset_groups_2c31ee932fc71edcb66a09c2.

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 mention of alternatives such as the base get_asset_groups tool, and no prerequisites. The only actionable hint is the pointer to describe_operation for native request schemas, which is a schema-lookup instruction rather than usage guidance.

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