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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavioral context beyond that: the response is voluminous, which is a cost/payload warning an agent needs when deciding whether to call it. It does not cover the project-targeting/authorization behavior, but the schema handles that.

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?

A single sentence that front-loads the return payload and closes with the disambiguating alternatives. No filler; every clause carries information.

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 compensates by naming the returned contents and warning about volume. Combined with annotations covering read-only status and the schema covering the project-targeting parameter, an agent has everything needed to invoke this correctly.

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 description mentions no parameters at all; it adds nothing about expectedProjectId, which the schema already documents in detail (UUID format, targets this project instead of the session project, refused without access). With 50% coverage and one 'placeholder' param (_unused) left undocumented, 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?

Specific verb ('Returns') plus precise resource ('the entire schema') and an explicit enumeration of what that contains (blocks, people, dependencies). It is immediately distinguishable from get_schema_overview and get_cell_details, which it names as narrower scopes.

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?

It routes the agent to alternatives by stating that get_schema_overview narrows to an overview and get_cell_details to a single block, and signals that this tool is the heavy option ('voluminous response'). It doesn't give an explicit 'call this only when...' trigger, but the trade-off is clear enough to choose correctly.

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