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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description still adds real behavioral context beyond that: responses are 'private, no-store', revocation immediately blocks this download with an existing session or key, the initial grant requires the owner's session with origin and CSRF checks, and org API keys stay within existing grants. Some paragraphs (sharing collections) are platform-wide policy rather than tool-specific, keeping this below a 5.

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?

The purpose is front-loaded in sentence one and is crisp, but the description then runs roughly seven more sentences of platform-wide policy (collection sharing, ownership of sharing, publishing rules) that do not describe this ZIP-download tool. Several sentences ('Sharing does not publish a resource. Only the resource owner changes sharing.') carry no actionable information for invoking this tool.

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 read-only binary export with annotations covering the safety profile and no output schema, the description supplies the important missing context: caching headers, revocation behavior, and the session/key requirements for the underlying grant. It is largely complete, with the only real gap being explicit differentiation from the other export tools.

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 description coverage is 100%, so the schema already documents base_id (64-character ID) and organization_id (must come from list_knowledge_teams, active membership and OKFIndex required). The description adds no syntax, format, or semantics for either parameter beyond what the schema states, so the baseline 3 applies.

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?

"Get the private OKF ZIP download" states a specific verb (get/download) and resource (private OKF ZIP). However, it never distinguishes this from the sibling export_base or public_export_base, so the agent must infer that the 'team_' prefix means team-scoped access. The second sentence hints at team membership semantics but does not explicitly contrast with the non-team variants.

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 description implies usage via the access model ("Team access uses current account membership, product access and resource sharing on every request"), which tells the agent this requires team membership. But there is no explicit when-to-use/when-not statement and no routing to export_base or public_export_base, which is the key decision an agent faces given three near-identical siblings.

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