workiva_wdata_get_table

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

With no annotations provided, the description must disclose behavior itself, but it only says 'Get' without describing side effects, return format, authentication needs, or error behaviors. No additional context is offered beyond the immediate action.

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 very short and to the point, with the main statement front-loaded and no filler. It is appropriately sized for a simple single-parameter get operation, though its brevity borders on under-specification.

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?

Given the tool's simplicity and the presence of an output schema, the description is minimally viable. It lacks differentiation from related table-focused tools and fails to mention when to use this over get_table_properties, but it does cover the essential 'fetch by ID' semantics.

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 input schema has 0% coverage and the description provides a minimal arg line 'table_id: The Wdata table ID', which essentially restates the schema title 'Table Id'. It does not explain the ID's format, origin, or how to locate it, failing to substantially compensate for the schema gap.

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 action 'Get' and the resource 'a single Wdata table', which identifies the tool's core function. However, it does not explicitly differentiate it from similar sibling tools like workiva_get_table_properties or workiva_get_table_columns, which could lead to confusion about scope.

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 list_tables or get_table_properties. There are no usage scenarios, prerequisites, or exclusions mentioned, leaving the agent to infer applicability.

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