Get Ops Operation Status (admin)

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

Annotations already declare the operation read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond annotations: it explains polling lifecycle status, that includeResult fetches the result payload only once complete, and that admin credentials (FUTPICKS_OPS_TOKEN) are required.

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 carry all essential information with front-loaded purpose, followed by optional behavior and auth requirement. Every word earns its place.

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 two-parameter read-only status tool with rich annotations, the description covers purpose, result-fetching option, and auth context. It could be slightly more explicit about what lifecycle states to expect or that the result is unavailable until completion, but those are minor gaps with no output schema.

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 coverage is 100%, so the baseline is 3. The description adds meaningful semantics beyond schema by clarifying that includeResult=true fetches the result payload after the operation completes, and frames id as the operation identifier being polled.

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 uses a specific verb and resource: 'Poll an operation's lifecycle status by id.' It also states the optional result payload behavior and admin-only access, making the tool's purpose immediately clear and distinct from sibling operations tools like flab_ops_run.

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 usage: call it with an operation id to poll status, optionally including the result payload once complete. It does not explicitly state when to prefer this tool over alternatives or mention the related flow with flab_ops_run, though the schema's 'id (from flab_ops_run)' provides some implicit context.

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