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

Annotations already declare readOnly=true, idempotent=true, destructive=false, so the safety profile is covered. The description adds genuinely useful context beyond that: it enumerates the return surface (data.settings, editable_fields, can_update, requires_version, ai_mutation_version) and explains that site-level schema is generated from these settings, which is non-obvious behavior.

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?

Front-loaded with the action and its purpose, then the return contract, then the coverage list. Efficient and well-ordered; the enumerated coverage list is slightly long but each item is informative.

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?

An output schema exists, so the return-value detail is arguably redundant but reinforces the contract. Purpose, coverage, and mutation-versioning context are all present; only the lone input parameter goes undescribed.

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%, so the description carries the burden for the single project_id parameter, yet it never mentions it or its format. The parameter is trivially self-explanatory, warranting minimum viable rather than penalized, but no added meaning is provided.

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+resource ('Read Grigora's existing SEO settings') and frames it against the write path ('before making SEO/schema changes'), which cleanly distinguishes it from the sibling update_seo_settings. An agent knows exactly what this does 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?

Gives clear context: use it before making SEO/schema changes, implicitly positioning it as the read prerequisite to update_seo_settings. It stops short of naming the alternative sibling or stating exclusions, so it's strong but not exhaustive.

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