Next move

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that it returns a single prioritized item rather than a list and that it includes a handoff, which is genuinely useful beyond the annotations, but it stops short of explaining what the handoff contains or how the item is ranked.

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 tight sentence with no filler, and the essential concept is front-loaded. It reads as a fragment ('with its handoff') whose referent is unclear, which slightly undercuts crispness.

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?

With no output schema, the description carries the full burden of describing the return value, and it only gestures at it ('the single next thing ... with its handoff'). An agent knows the flavor of the response but not its shape, so it is minimally adequate for a zero-param read tool.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. No parameter guidance is needed.

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?

It conveys that the tool surfaces a prioritized next item plus a handoff, but the phrasing is abstract ('the single next thing that needs attention') rather than a clear verb+resource. With no output schema, an agent cannot pin down what object it actually returns or how it differs from siblings like forbiz_state or forbiz_get_action.

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 a faint implication of when to call it (when you need to know what to do next), but no explicit when/when-not and no routing to alternatives. Given ~19 siblings covering state, actions, and history, the absence of any differentiation is a real gap.

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