workiva_import_style_guide

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Import a style guide' does not mention side effects, permissions, reversibility, or what happens to existing data, which is a significant gap for a potentially mutating operation.

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 compact and front-loaded with the operation statement, followed by a minimal Args block. It is appropriately sized for a single-parameter tool, though the brevity partly reflects under-specification rather than polished conciseness.

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 no annotations and minimal schema descriptions, the description is incomplete. It fails to explain the operational effect of importing, any prerequisites, or how it relates to sibling style-guide tools, even though an output schema exists.

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?

With 0% schema description coverage, the description compensates by explaining that style_guide_id is a UUID, which adds type clarity beyond the schema's 'Style Guide Id' label. However, it does not explain how to obtain the ID or provide additional format guidance.

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 states 'Import a style guide' with a specific verb and resource, which clearly identifies what the tool does. It is somewhat distinguished from siblings like workiva_get_style_guide and workiva_export_style_guide by the import/export direction, but it does not explicitly differentiate its scope or semantics.

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?

There is no guidance on when to use this tool versus alternatives such as get_style_guide or export_style_guide. The description gives no context, prerequisites, or exclusions, leaving the agent without usage direction.

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