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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, and the description's verb 'Read' merely restates that. Nothing is said about ordering of audit entries, what a change record contains, retention window, or pagination behavior via limit/offset — the kind of context that would actually add value on top of the annotations.

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 short sentence with zero filler, so nothing is wasted, but the terseness reflects under-specification rather than disciplined compression. Nothing is front-loaded beyond the bare purpose.

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 read tool with no output schema, the description should at least sketch what an audit entry includes and how the history is ordered and paginated. With three undocumented parameters and no return-value context, an agent cannot tell what to expect back or how to page through results.

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% — the three parameters (campaign_id, limit, offset) carry only titles and numeric bounds. The description says nothing about what campaign_id must refer to or that limit/offset paginate a chronological history (default 50, max 200 is not explained as a page size). The description does not 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 the change history of your campaign' — which is distinguishable from siblings like get_campaign (current state) and get_profile_audit (different resource). It does not explicitly contrast with those siblings, but the resource is concrete enough for an agent to select it.

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?

No guidance on when to use this instead of get_campaign or get_profile_audit, no mention of prerequisites (e.g., must own the campaign), and no exclusions. The agent must infer applicability from the resource noun alone.

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