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

The annotations already establish readOnly=true, idempotent=true, and destructive=false, while the description adds meaningful context about read limits, paid-capacity behavior, private-by-default bases, no-store responses, and treating uploaded text as untrusted data. Some of the policy detail is broader than this single tool, but the description still substantially exceeds the annotations.

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, but the description runs long and includes policy sentences about billing, publishing, upload/replacement, and removal that are only indirectly relevant to get_base. Several sentences could be trimmed without reducing clarity for 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?

With no output schema, the description should more fully explain what get_base returns and how the after cursor is used. It does add useful security and privacy context, but it leaves the response shape and pagination semantics under-specified.

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%, so the schema already documents both base_id and the after cursor. The description does not add parameter-specific meaning beyond the schema; for example, it does not clarify what the cursor paginates over or what the returned base object contains.

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 has a clear verb and resource in 'Read your base and its documents', but it does not distinguish this tool from siblings like get_base_document, list_base_documents, or public_get_base. The phrase 'and its documents' also makes the intended scope somewhat ambiguous.

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 says to read a base but gives no explicit guidance on when to use this tool versus get_base_document, list_base_documents, search_base, or team/public variants. It also does not tell the agent how to obtain the required base_id, for example via list_bases.

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