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 'Classification: read-only' is largely redundant. The description does add non-structured traits though: 'Execution: synchronous' and 'Task support: forbidden,' plus output presentation guidance.

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?

Purpose is front-loaded, but the title text is duplicated at the start of the description and there is a doubled period ('authority..'). Roughly half the text is generic presentation boilerplate (assistantSummary, never display raw JSON) rather than tool-selection information.

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 explained, and deprecation is disclosed. However, for a tool with 16 parameters, nested objects, and 0% schema descriptions, the description gives an agent no help in constructing a valid call beyond the required eventIds.

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% across 16 parameters with only eventIds required, and the description explains none of them. Nested objects like marketContext and marketLanguageProfile are entirely undocumented, so the description fails to compensate for the coverage gap.

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 ('Read scoped verified event attestations') and bounds scope with 'no publication authority,' which the agent cannot get from the name alone. It also identifies itself as a 'Deprecated alias for get_world_activation_evidence,' differentiating it from that sibling.

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 'Deprecated alias' label implies the canonical tool should be preferred, giving implicit routing guidance, but there is no explicit 'use get_world_activation_evidence instead' instruction or condition. No when-not or prerequisite context for approval/activation workflows is provided.

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