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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds what the payload surfaces (latest plan with counts, recent batches with outcomes, verified/cancellable flags), which is genuinely useful, but it stops short of richer context such as retention windows, pagination of 'ultimi lotti', or authorization needs.

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 dense sentence with the resource front-loaded and the return contents enumerated in a parenthetical; nothing is wasted. Slight cost: the parenthetical is terse and written in Italian while the tool name and annotations are English, but the size is well matched to the tool's simplicity.

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 must carry the return-value burden; it partially does by naming the plan/batch contents and the verified/cancellable flags, but 'ultimi lotti' and 'conteggi' remain undefined in scope. For a simple read-only single-parameter tool this is adequate but not complete.

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?

There is a single optional parameter with 100% schema description coverage that already explains account_id, the outpost concept, and the single-outpost default. 'per l'outpost' in the description only echoes the schema, so the baseline of 3 is appropriate with no added value.

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 resource and the operation clearly: 'Titolo-SEO: stato per l'outpost', with a parenthetical enumerating what the status contains (latest plan with counts, latest batches with outcome, verified, cancellable). The verb is a noun phrase ('stato') rather than an action, and it doesn't differentiate itself from sibling tools such as plan_title_seo_fix or title_seo_rollback, so it falls short of a 5.

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?

There is no indication of when an agent should call this instead of plan_title_seo_fix, apply_title_seo_batch, title_seo_rollback, or audit_title_compliance. Usage is only inferable from the word 'stato'. No prerequisites or exclusions are given.

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