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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description does add one genuinely new behavioral fact — that the connector does not read accounts, collections or private notes — which is a useful data-boundary disclosure, but says nothing about count freshness, caching, or cost.

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?

Two short sentences with no filler, and the scope statement is front-loaded before the privacy caveat. It is efficient, though the fragmentary noun-list style makes it slightly less scannable than a verb-led sentence would be.

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 return values need not be explained, and a zero-parameter read-only info tool has modest requirements. What is still missing is routing against the near-identical sibling archive_coverage and any indication of how current or authoritative the reported counts are.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to carry. Baseline 4 applies; nothing is misdocumented or missing on this dimension.

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?

The description names the resource content ('ambito dell'archivio, conteggi misurati e regole di uso delle fonti'), which tells the agent roughly what comes back, but it uses no verb and reads as a noun list. It also fails to distinguish itself from the sibling archive_coverage, whose name suggests heavy overlap with 'ambito/conteggi'.

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 statement of when to call this tool, when not to, or which sibling to prefer (archive_coverage, search, fetch). The agent must guess from the name alone. The privacy sentence is a scope note, not usage guidance.

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