yaaif_ambient_workflow_get

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It only says 'Get', which implies read-only, but it does not state what is returned, how errors such as not-found are handled, whether any permissions are required, or if there are side effects.

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 a single short sentence with no filler. Every word contributes to stating the tool's purpose, and the core action is front-loaded.

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?

Despite the tool's low complexity, there is no output schema and no annotations, so the description should clarify what the caller receives and any important behavioral caveats. It only states the action, leaving the return value, error behavior, and relationship to sibling tools to be inferred.

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%, but there is only one required parameter with a self-explanatory name. The description's 'by id' aligns with the workflow_id property, providing minimal confirmation of its meaning. It does not specify format, examples, or where the id comes from, but this is sufficient for a single simple string parameter.

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?

Description uses a specific verb ('Get'), a resource ('ambient workflow'), and a selection criterion ('by id'). This clearly distinguishes it from sibling list tools like yaaif_ambient_workflow_list and from yaaif_ambient_run_get, which targets runs rather than workflows.

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?

No guidance is given on when to use this tool versus alternatives such as yaaif_ambient_workflow_list or yaaif_ambient_run_get. There is no mention of prerequisites, when a single workflow lookup is appropriate, or how this relates to workflow management workflows.

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