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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful behavioral context: live headlines, separate human and agent ratings, model voting, Arbiter confirmation counts, and the explicit stance that Orb Studio makes no forecasts and only shows agreement.

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 dense but front-loads the core identity and then enumerates the included data categories efficiently. It is somewhat run-on, but nearly every clause conveys distinct scope information.

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 input parameters and no output schema, the description carries the burden of explaining what is returned, which it does across instruments, crises, headlines, exit paths, ratings, consensus, model votes, and Arbiter checks. It does not describe response structure or size, but is otherwise complete for a read-only dashboard 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?

There are zero parameters, so parameter semantics are minimal by definition. The schema is fully described and the description correctly implies this is a no-argument aggregate retrieval tool.

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 this is a planetary 'captain's bridge' that aggregates crisis instruments, current crises, exit paths, human/agent ratings, consensus, model votes, and an Arbiter check. It distinguishes the tool's content from generic crisis or voting tools, though it does not explicitly name siblings like get_crisis or propose_exit_path.

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 explains what the bridge contains but gives no guidance on when to use it versus alternatives such as get_crisis, propose_exit_path, rate_exit_path, or get_vote_results. With many sibling tools, the absence of routing guidance is a notable gap.

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