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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely non-obvious traits: per-plan read limits, post-expiry read-only access, private no-store responses, and an explicit prompt-injection warning that uploaded text is untrusted data. Those are real behavioral facts beyond the structured fields, though several sentences (purchase, removal, upload) describe other tools' behavior rather than this call.

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 one useful identification sentence is buried at the front of a dense block of account policy, billing, publishing, and deletion rules. Sentences like "Purchase requires an explicit browser action; an API key cannot buy a subscription" do not earn their place in a read-index tool's description.

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?

With no output schema, the description must convey what an index response contains, and it does not — is it a document tree, metadata listing, or a manifest? It also never clarifies how this differs from get_base or list_base_documents, so an agent still has to guess before calling it.

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?

There is a single parameter with 100% schema description coverage ("the 64-character ID returned by the API"), so the schema already carries the semantics. The description adds nothing about base_id, which is acceptable at full coverage but earns only the baseline.

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 first sentence names a verb and resource ("Read the private OKF root index"), but "OKF root index" is unexplained jargon and the description never differentiates this from close siblings like get_base, list_base_documents, public_read_base_index, or team_read_base_index. An agent can tell it is a read, but not what makes it distinct.

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 at all: nothing says to pick this over list_base_documents, get_base, or read_base_markdown, and no mention of the team_/public_ variants that clearly mirror this tool. The stated limits and account policy describe constraints, not selection criteria.

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