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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description contributes context beyond them by scoping results to the account and disclosing what is deliberately withheld (private briefs, credentials), which is exactly the kind of behavioral detail annotations can't express.

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?

A single sentence with the scope and exclusions front-loaded and no filler. Every clause (account scope, contents, withheld data) earns its place.

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-value explanation isn't needed, and the privacy boundary is well covered. However, the pagination contract (limit/cursor) is the main thing an agent must get right to call this correctly, and it is absent.

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 for 'limit' and 'cursor' — and it says nothing about them. It doesn't explain that results are paginated, what limit defaults to (10), or how to page with cursor, leaving both parameters opaque beyond their bare types.

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 ('Read'), resource ('this account's recent MCP activity'), and enumerates the content ('operations and consulted scene IDs'), which lets an agent distinguish it from data-fetching siblings like get_scene or search_scenes. It stops short of naming an alternative, but no sibling overlaps this retrieval role.

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?

Usage is implied by 'recent activity' — an agent can infer this is for auditing prior operations — but there is no explicit when-to-use, when-not-to-use, or pointer to a sibling for related needs (e.g. detail lookup via get_scene).

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