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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's real contribution is the account scoping constraint and the conn_id stability semantics — non-obvious behavior an agent would otherwise have to discover empirically. It says nothing about ordering or whether the window is time-bounded, which is the remaining behavioral gap.

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 result fields are front-loaded, then the clarification that conn_id is session-stable follows as supporting detail. The client_id/conn_id comparison is the longest clause but earns its place by explaining a distinction the reader would otherwise get wrong; minor tightening is possible in "which client_id cannot show because every connection from one AI platform reports the same client."

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 prose, and the single input parameter is schema-documented. The account scoping line closes the main correctness risk; only the ordering of "recent" events and any pagination beyond limit are left unstated.

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 100% and the single limit parameter is fully documented in the schema including its default of 25 and its 1-100 bounds, so the description owes it nothing. Per the high-coverage baseline this is a 3; the description adds no paging or ordering meaning beyond the schema.

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?

"Lists this account's recent MCP activity" pairs a specific verb with a specific resource, then enumerates the returned facets (tool, runtime, client, session, allowed/denied), which makes the tool's scope unmistakable against list_history / list_orders / list_runtimes. It stops short of naming a sibling explicitly, so it sits just under a 5.

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?

No statement of when to reach for this over spotgrid.list_history or spotgrid.get_usage, and no stated prerequisites. Usage is only implied by the conn_id discussion, which suggests it is the tool to use when you need to tell two sessions from the same AI platform apart.

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