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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds ordering (newest first) and the content of each change entry, but says nothing about pagination behavior, truncation at the limit, or whether history is complete or retained.

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, front-loaded sentence with a colon-delimited list of return fields. No filler; every clause conveys information about what the agent will get back.

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?

With no output schema, the description does carry the burden of describing returns and does so reasonably (time, actor, before → after). However, it omits pagination/limit semantics beyond the schema default and leaves the required table/record_id parameters unexplained, which is a gap for a tool whose schema coverage is low.

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 only 33%: limit is documented ('Max 50, default 20') but table and record_id have no descriptions at all. The description does not mention any parameter, so it fails to compensate for the undocumented required parameters (e.g., what table values are valid, what record_id accepts).

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 names the resource (a record's change history) and specifies the returned content precisely: timestamp, actor type (user/automation/AI), and before → after values. This distinguishes it from nearby siblings like compare_record or list_deleted_records, though it never states the operation as a verb or explicitly names a sibling it is not.

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 guidance on when to use this tool versus alternatives such as compare_record, activity_summary, or list_deleted_records, and no stated prerequisites or contexts. The agent must infer usage purely from the noun phrase.

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