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

With no annotations, the description carries the full behavioral burden and does so: it declares zero cost, no scanning side effect, newest-first ordering, what each entry contains, and how edge cases appear ('Blocked and failed scans are listed without a score'). That is unusually complete disclosure of side effects, ordering, and degraded-record handling.

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 what is listed and in what order, then cost/side-effect, then purpose. Every sentence contributes a distinct fact with no 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 simple one-parameter read tool with no output schema, the description covers return contents, ordering, and edge cases well. It does not mention result limits or pagination behavior for very long histories, a minor remaining 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 there is a single required url parameter whose schema description already explains exactness and trailing-slash sensitivity. The description's 'one exact page' reinforces but adds no syntax beyond the schema, 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?

Specific verb+resource: 'List every stored Bot Appétit scan of one exact page', plus ordering ('newest first') and payload ('score at the time and how it moved'). The phrase 'one exact page' implicitly separates it from site_history, but it never names that sibling explicitly, so an agent must infer the distinction.

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 a clear use case ('Use it to show whether a page has improved') and a relevant precondition ('Costs nothing and does not scan'), which tells the agent this is the cheap read-only alternative to running a scan. No explicit when-not or named alternative (e.g. site_history for whole-site timelines) is provided.

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