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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds a scoping note ("Returns live workspace data, not an interview transcript"), which usefully clarifies the data source, but says nothing about pagination, filtering, or result ordering.

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?

Two short sentences with the trigger condition front-loaded and no padding. The second sentence is slightly cryptic out of context but still earns its place by clarifying the data source.

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?

An output schema exists so return values needn't be explained, and annotations cover the safety profile. However, for a 5-parameter filtered-list tool with zero param descriptions, the absence of any guidance on filters or paging leaves real gaps.

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% across 5 parameters, so the description carries the full burden — and it contributes nothing about limit, query, cursor, status, or department. The names and enums are largely self-explanatory, which keeps this above a 1, but pagination semantics for cursor/limit are entirely undocumented.

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?

States a clear verb (find/compare) and resource (saved workflows in the Revensi workspace), and the singular sibling get_workflow is implicitly contrasted by the list semantics. It does not, however, explicitly distinguish itself from siblings like get_workflow or list_workflow_questions.

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?

"Use this when the user wants to find or compare saved workflows" gives a usable trigger condition, which is more than most list tools offer. But it names no alternatives and no exclusions, so an agent must infer when to prefer get_workflow over this.

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