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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds governance context (MCP approval configuration, business workflow approvals always apply), but those points pertain to changes, not to this read operation, so they add limited value for invoking it.

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?

Three short sentences, but only the first addresses the read action; the remaining two are approval-policy boilerplate that does not help an agent decide or invoke. The relevant content is front-loaded, so it is efficient but padded.

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?

It is a simple one-parameter read with an output schema and read-only annotations, so much is covered elsewhere. However, the missing explanation of folderId and the mismatch between 'vendor portal visibility' and document folder visibility leave a gap an agent must guess at.

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 single parameter folderId has 0% schema description coverage — only format and pattern are given — and the description never mentions it. The agent gets no explanation of what folder identifier to supply or where it comes from, so the baseline-4 allowance for zero-parameter tools does not apply.

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 verb 'Read' is specific, but the resource is named as 'vendor portal visibility' rather than document folder visibility, leaving the agent to reconcile the description with the tool name. It never states that it returns the visibility settings of documents in a specific folder, so the purpose is only inferable.

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?

The closest thing to guidance is 'Sharing changes require explicit review', which hints that modifications go elsewhere but never names set_document_folder_visibility or explains when to choose this read over get_site_document_visibility. There are no explicit conditions or exclusions.

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