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 safety profile is covered. The description adds genuinely useful context the annotations don't: the account session requirement (browser cookie + CSRF). However it says nothing about pagination direction, result set size, or what is returned.

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 precedes the precondition. It is efficiently written, though the brevity comes partly from omitting necessary information rather than from tight editing.

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 single-optional-parameter read tool with an output schema absent, the auth requirement is the most important missing piece and it is supplied. The definition still leaves unclear what the tool actually returns and how it differs from the crowded document-tool family, which is the key ambiguity an agent faces here.

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 coverage is 100% and the sole cursor parameter "antes" is already documented in the schema as an exclusive client cursor. The description adds no pagination semantics beyond that, so the baseline 3 applies when the schema does all the work.

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?

"Coleção privada da conta" names a resource and scope but no verb — it doesn't say whether the tool lists, fetches, or searches documents. It also does not distinguish itself from the many document siblings (documento, documentos_empresa, documento_leitura), so the agent must infer purpose from the name alone.

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 use this tool versus documento, documentos_empresa, or the other documento_* siblings, nor any exclusion criteria. The only directive is the auth prerequisite, which is a precondition rather than usage guidance.

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