get_content_history

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

Annotations only cover readOnlyHint and openWorldHint, so the description adds real value: it explains how to paginate via pagination.hasMore and, critically, the interpretation rule that a null means an unreadable sitemap and never a measured zero. That semantic warning prevents a serious misreading of results.

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?

Three short sentences, front-loaded with the core purpose, then pagination mechanics, then the null-semantics caveat. Every sentence earns its place with no filler 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?

For a read-only listing tool with no output schema, the description supplies the two things an agent most needs: how to page through results and how to interpret null values. It stops short of characterizing what each run record contains, but the essential calling information is present.

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 100%, with page, limit, and projectId all documented including defaults, bounds, and provenance (from list_projects). The description adds no per-parameter detail, so the baseline of 3 is correct when the schema carries the load.

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: "Get paginated history of Content Intelligence monitoring runs." That clearly separates it from get_content_run_detail (single run) and get_content_dashboard (current state), though it never names those siblings explicitly. The scope is unambiguous without opening the schema.

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 implies usage (fetching the run history) and gives operational instructions for pagination, and it references get_content_dashboard for the reading rule. But it never states when to prefer this over get_content_run_detail or get_content_changelog, so the agent must infer the selection boundary.

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