workiva_get_sheet

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

With no annotations provided, the description simply says 'Get details', implying a read operation but disclosing no error behavior, permissions, or side effects. No context on what happens for invalid UUIDs or whether cell contents are included.

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?

Description is one line plus an Args list; every element is necessary. No filler or repetition of the schema.

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?

Has an output schema, so return format is covered, but for a tool among many siblings, the description should clarify that 'details' means sheet metadata/properties and not cell data. Args are documented, but the ambiguous scope leaves the tool incomplete for an agent deciding between this and workiva_read_cells.

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 has no descriptions (0% coverage), and description adds minimal meaning by labeling each argument as a UUID. It does not explain how to discover these IDs or distinguish spreadsheet_id from sheet_id beyond their names, but it does provide a key type hint.

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?

Description uses explicit 'Get details for a single sheet', clearly distinguishing from list-oriented siblings like workiva_list_sheets and get_spreadsheet. However, 'details' is vague about whether it returns metadata vs content, so not a 5.

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?

No guidance on when to choose this over workiva_list_sheets, workiva_get_spreadsheet, or workiva_read_cells. No exclusions or alternatives named; only states the tool's basic function.

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