workiva_get_spreadsheet

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Get' implies a read-only operation, but the description does not explicitly state that it avoids side effects, what permissions are required, or what the response contains beyond 'details.' The expand parameter hints at subresource inclusion but lacks elaboration on default behavior.

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 concise and front-loaded with the purpose. It uses a simple one-line summary followed by a clear argument list. Every word adds value, with no redundancy.

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?

The tool is a simple fetch operation with an output schema, so return details are not needed in the description. However, the description lacks any context about prerequisites (e.g., needing to obtain spreadsheet_id from a list call) or how this relates to other spreadsheet tools. It is minimally viable but lacks guiding context.

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 schema provides only type and default, but the description adds meaningful semantics: spreadsheet_id is identified as 'the spreadsheet UUID' and expand is explained as 'comma-separated subresources to include' with an example. This compensates for the 0% schema description coverage.

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 states the tool retrieves spreadsheet details, which is a specific verb+resource. It is distinct from siblings like workiva_list_spreadsheets (list all spreadsheets) and workiva_get_sheet (get a sheet within a spreadsheet), though it does not explicitly differentiate itself.

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 provides no guidance on when to use this tool versus alternatives, such as workiva_list_spreadsheets for listing or workiva_get_sheet for individual sheets. No usage scenarios or exclusions are mentioned.

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