get_sheet

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

No annotations provided, so description carries full burden. Describes depth effect, concurrency rev recording, and stub behavior for nested boards. References get_node for deeper fetching.

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?

Single paragraph, 4 sentences. Purpose is front-loaded. Efficient but could be slightly more concise.

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?

Adequate for a read tool with clear sibling context. Concurrency behavior is explained in relation to save_sheet. No output schema, but return format is not critical for function selection.

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%, but description explains depth as positive integer controlling nesting and sheet as id. Adds value beyond schema by hinting at behavior when depth is omitted or used.

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?

Clearly states 'Read ONE workflow sheet by id' with specific verb and resource. Distinguishes from sibling tools like list_sheets (list all) and get_node (fetch nested boards).

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?

Provides explicit guidance on depth parameter usage ('Omit depth for the full sheet') and concurrency behavior. Does not explicitly state when not to use the tool, but context is sufficient.

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