get_sheet

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

With no annotations present, the description carries the behavioral disclosure burden. It does reveal that the tool returns placement warnings and title block fields, which is useful. However, it does not explicitly state that the operation is read-only, how the 'page' parameter changes behavior, or what happens for missing/invalid input.

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 description is extremely concise with no filler words, and it leads with the sheet resource. It is slightly elliptical because it is a noun phrase rather than a complete sentence, but it earns high marks for economy.

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?

An output schema exists, so return value structure is partially covered, but the description still leaves key gaps: the 'page' parameter is semantically undefined, no usage context is provided, and there is no guidance about which sibling tools to prefer. For a one-parameter getter this is underwhelming.

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 0% and the description does not mention the 'page' parameter at all. The parameter name gives a minimal hint, but its meaning, allowed values, and the effect of the default null are entirely unexplained.

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 clearly identifies the resource (the sheet) and enumerates the specific data returned: format, scale, title block fields, and plan placement warnings. It lacks an explicit verb, but the tool name 'get_sheet' supplies the action, and the listed aspects distinguish it from sibling getters such as get_document and get_bounds.

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 gives no guidance on when to use this tool versus alternatives. Sibling tools like set_scale, add_title_block, position_view, and get_bounds are conceptually close, but the description provides no trigger conditions, exclusions, or selection criteria.

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