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 fully covered elsewhere. The description adds no behavioral context of its own — no pagination, filtering, or scope information — beyond pointing at describe_operation for schemas.

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 text is short but wasteful: the identical sentence appears twice, and the operation ID is a machine artifact of little use to an agent choosing a tool. There is no front-loaded statement of purpose to justify the brevity.

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, 0% parameter description coverage, and nested objects, this definition should carry more explanatory weight than it does. The describe_operation hand-off partially mitigates the schema gap, but an agent still cannot tell what this call retrieves or how to shape the query.

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% for two nested parameters (a free-form 'query' object and an empty 'params' object), so the description must compensate and does not. It gives no indication of what belongs in 'query' or why 'params' is constrained to no properties, leaving the delegation to describe_operation as the only thread for the agent to pull.

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 restates the tool title verbatim ('GET /api/asset-groups') and repeats it, with no verb-level explanation of what an asset group is or what is returned. An agent learns only that this is a GET on the asset-groups resource, with no differentiation from siblings such as get_asset_groups_by_id_history_baa8444d4c960eb2b28a3031.

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 only actionable guidance is the pointer that 'describe_operation provides native request schemas', which tells the agent where to look for request shape but not when to call this tool versus its siblings. There are no conditions, prerequisites, or exclusions stated.

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