is_get_workflow

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

No annotations are provided, so the description carries the full burden. It correctly indicates a read operation (status and history), but does not disclose permissions, rate limits, or what 'history' precisely entails. It is adequate but not exhaustive.

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?

A single sentence that front-loads the verb and resource, with examples. Every word contributes to understanding. No unnecessary information.

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?

For a simple retrieval tool with one parameter and no output schema, the description covers the essential purpose and scope. It would benefit from a brief note on the output structure, but is sufficiently complete given the simplicity.

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 has 100% coverage for the single parameter workflow_id, so baseline is 3. The description adds no further detail beyond the schema's 'Workflow instance identifier'; it does not explain how to obtain the ID or any expected format.

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 explicitly states the tool retrieves 'current status and history' of an iSuite workflow instance, with concrete examples of workflow types (underwriting approvals, claim processing, compliance reviews). This differentiates it from sibling tools like is_list_my_workflows (listing) and is_get_workflow_logs (logs).

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 implies the tool is for obtaining detailed status/history of a single workflow, which is clear given siblings that list or advance workflows. However, it lacks explicit when-to-use or when-not-to-use guidance, such as suggesting is_list_my_workflows for overviews.

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