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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond them: settlement is not independently revalidated, live learned selection and exploration are withheld with zero allowance, and private inspection is excluded. This is meaningful disclosure of data-provenance and staleness limits.

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 purpose is front-loaded and most sentences are terse, but the middle is an unstructured noun list of returned artifacts and the value is diluted by repeated negative clauses ('No questions, wallets or receipt identifiers' ... 'No research, source read, payment...'). Some sentences earn their place; the list-style fragments are harder to parse than prose.

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?

For a tool with no output schema, the description usefully enumerates the returned fields (topics, counts, citation contribution, average access price, uncertainty, shift flag) and behavioral limits. But the sole input parameter is undocumented and there is no statement of the identifying key's meaning, so an agent could call it without understanding what sourceId must be.

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?

There is a single required parameter (sourceId) with 0% schema description coverage, so the description carries the burden of explaining it. It never mentions sourceId, its format, or what constitutes a valid identifier, leaving the agent with only the regex/pattern in 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?

The description gives a specific verb ('Read') and a resource ('bounded observational source/topic record') and constrains scope to write-time independently classified/funded outside observations. However, the phrasing is heavily jargon-laden ('bounded observational source/topic record', 'recorded citation contribution') and never names or contrasts any sibling tool, so the agent must infer which read tool among the many history_* and profile_* siblings applies.

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?

It states qualification rules (only write-time independently classified/funded outside observations; owners, unknown and private history excluded) and lists negative capabilities (no research, source read, payment, private inspection or policy activation), which implicitly routes away from sibling tools like research or history_private_jobs_read. But there is no explicit 'use this when' or named alternative, so the guidance is implied rather than directive.

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