yaaif_ambient_run_get

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. It only states that the operation is a get, which implies a read, but says nothing about not-found behavior, access requirements, response shape, or any side effects. For a tool with zero annotation coverage, this is minimal.

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. It is front-loaded with the verb and object, and every word contributes to the core meaning.

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 one-parameter retrieval tool, the description is minimally sufficient to make a basic call. However, it omits any context about what an ambient run is, what the response contains, and how this tool relates to the many nearby run-related siblings, leaving an agent with some ambiguity.

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 0% description coverage and the sole parameter run_id is only typed as a string. The description's 'by id' adds little beyond the parameter name itself; it does not explain what kind of id, where to find it, or any formatting constraints.

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 a clear verb ('Get'), a specific resource ('one ambient run'), and the identifying mechanism ('by id'). It is distinguishable from list-style siblings like yaaif_ambient_runs_list, though it does not explicitly differentiate itself from the similarly named yaaif_ops_ambient_run_get.

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 yaaif_ambient_runs_list or yaaif_ops_ambient_run_get. The description implies a by-id lookup but provides no conditions, exclusions, or mention of sibling tools.

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