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

Annotations already declare readOnlyHint=false and destructiveHint=false, so 'record' is consistent with a non-destructive write. However, the description adds nothing further: it never explains confirmStacked (which implies stacked/bundled changes need confirmation), the before/after capture behavior, or any auth/rate constraints.

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 no filler, and the purpose clause is placed last for impact. It is efficient, though arguably too terse for a 9-parameter mutation tool.

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 write tool with 9 parameters, no output schema, and 0% schema coverage, the one-sentence description leaves too much undocumented. Critical semantics such as what before/after contain and what confirmStacked gates are absent.

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% across 9 parameters, so the description must carry the burden and largely does not. Only a loose mapping to pageUrl ('a change made to a page') is inferable; kind, before, after, note, changedAt, projectId, siteId, and confirmStacked are all unexplained.

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 (record/log) and resource (a change made to a page), and adds the downstream purpose (measuring search performance effect). The name and sibling 'list_seo_changes' make read vs write distinguishable, but the description never names the sibling to reinforce the contrast.

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?

The stated purpose ('so its effect on search performance is measured') implies why you would log a change, but there is no explicit when-to-use, when-not-to, or reference to alternatives such as list_seo_changes. Usage is only implied.

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