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

With no annotations, the description carries the full burden. It discloses real-timeness, token budget (~800 tokens), content scope, and auth requirements—useful behavioral context. However, it does not explicitly state that the operation is read-only or side-effect-free, and it omits details like rate limits or error behavior. This is moderate but not exceptional transparency.

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 two sentences and roughly 50 words, front-loaded with the core purpose. Every sentence adds value: the world model concept, token budget, covered topics, anchor contracts, and auth note. No wasted words or repetition.

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?

No output schema exists, but the description gives a good sense of the response content: ~800 tokens, specific topic coverage, and always-present anchor contracts. It does not describe pagination or detailed error handling, but for a simple snapshot tool with two optional parameters, it is fairly complete.

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%, meaning the schema already documents both parameters (focus and format) with descriptions. The tool description adds no additional parameter meaning beyond what the schema provides, so the baseline 3 applies.

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 it provides a real-time world model covering specific topics (geopolitics, economy, energy, etc.) with prediction market probabilities. The verb+resource is clear, but it does not explicitly differentiate from sibling tools like get_briefing or get_world_delta, so it falls short of a 5.

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 (when an agent needs a compact world state snapshot) and notes 'No auth needed', but it does not explicitly state when to use this tool versus alternatives or mention exclusions. No sibling tools are referenced, so guidance is only implicit.

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