bernstein_scenario_status

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 states the tool aggregates task status and returns JSON with status counts and per-task details. This conveys its read-only nature and output format adequately.

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 extremely concise: a one-sentence summary followed by a clear docstring with args and returns. Every sentence adds value without redundancy.

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 the single parameter and presence of an output schema (not shown but noted), the description covers the tool's purpose, input semantics, and output format. It could explicitly state the scenario must be running, but is sufficient.

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 only parameter, 'orchestration_id', has 0% schema description coverage. The description adds critical context by explaining it is 'Value returned by bernstein_scenario', which is beyond the schema's basic type and requirement.

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 clearly states 'Aggregate the status of all tasks of a running scenario', using a specific verb and resource, distinguishing it from siblings like 'bernstein_status' (likely overall status) and 'bernstein_tasks' (list tasks).

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 specifies that the input 'orchestration_id' is a value returned by 'bernstein_scenario', implying this tool should be used after launching a scenario. It does not explicitly mention when not to use it or alternatives, but gives clear context.

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