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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safe, repeatable read profile is covered. The description adds that the response concerns source health and archive size broken down into purchases and text documents, which is useful scope context, but it doesn't describe what 'health' means, what errors or statuses appear, or latency/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?

A single short sentence with no filler, and the resource ('origem', 'acervo') is front-loaded. It could be slightly clearer in wording, but nothing is wasted.

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 zero-parameter, read-only probe with annotations covering safety and no output schema, the description is minimally sufficient. However, without an output schema, the agent gets no idea what the returned health/size payload looks like or in what units the archive size is reported.

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 nothing for the description to disambiguate – baseline 4 applies. The schema is empty and fully consistent with the described no-argument probe.

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 states a resource and a rough capability: health of the source plus collection size for purchases and text documents. It is more than a tautology (the title 'Health' alone would be), but 'saúde da origem' is vague – it doesn't say which checks or metrics are reported, and no sibling is named or contrasted.

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 when-to-use guidance, no prerequisites, and no indication of when this diagnostic is relevant versus the many data-fetching siblings (compra, meus_documentos, etc.). The agent is left to infer that this is a status/health probe.

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