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

Annotations already declare readOnlyHint and idempotentHint, so the description's job is lighter. It adds valuable context by clarifying that the result is 'declared provenance plus timestamped bounded' observations and explicitly disclaims trust/safety/endorsement. This aligns with openWorldHint=false and does not contradict any annotation.

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 description is two compact sentences, front-loaded with the action and outcome. The second sentence is not filler; it prevents a meaningful class of misinterpretation. No unnecessary words or repetition.

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?

The output schema and annotations cover return shape and safety, and the description gives a clear domain-level picture. However, it omits pagination behavior, the role of subject_type, and any usage guidance, so an agent must infer several invocation details.

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%, and the description does not compensate. It never explains id, subject_type, limit, cursor, pagination, or the organic/sponsored distinction. The description adds no parameter-level meaning beyond what the input schema already shows.

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 states a specific verb ('Return') and a specific resource: declared provenance plus timestamped bounded conformance and reliability observations. The caveat 'Evidence is not trust, safety, quality, or endorsement' adds useful semantic precision. It does not explicitly differentiate from sibling tools, but the evidence-history scope is reasonably distinct.

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 explicit when-to-use statement or named alternative. However, the phrasing implies it should be used when provenance or conformance/reliability observations are needed, and the disclaimer provides a negative boundary: do not use this as trust or endorsement. This is implied guidance rather than explicit routing.

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