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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real context beyond them: results reflect a prior scheduled change check and do not re-read the site, and an agent key of read or write scope is required. However, it says nothing about staleness bounds, empty results, or what the check actually compares against.

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?

It is short and front-loaded, but the grammar is cramped ("rebuild is true when any did") and it introduces a field named rebuild that is never defined, which reads as jargon rather than clarity. Restructuring into two clean sentences about what is returned and what to do next would cost nothing.

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 carries the burden of explaining the return shape, and it only partially does so: it mentions pages and a rebuild flag but never says how pages are represented or what the full response contains. For a single-optional-parameter read tool this is adequate but leaves a real gap.

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 100%, and the trooth_id description already explains the default-to-own-company behavior. The description adds no parameter-level detail beyond what the schema provides, so baseline 3 applies.

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 the specific resource (pages of the newest version) and the specific query (what changed since the last read), plus the important qualifier that it comes from the scheduled change check rather than a live crawl. The phrasing "since it was read" is slightly ambiguous about what was read, but the intent is recoverable and distinguishable from siblings like semanto_versions_list and semanto_status.

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?

Gives an explicit branching instruction: when rebuild is true, call semanto_setup_read_again. That is genuine routing guidance that no other sibling provides. It stops short of stating when not to use this tool or how it differs from semanto_status or semanto_versions_list as a change-detection path.

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