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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is fully covered. The description adds useful scoping by calling the content 'canonical public protocol facts' (i.e., static reference data rather than live market state), but discloses nothing about freshness, versioning, or how the payload relates to the action flags it points to.

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 tight sentences with no filler; the topic enumeration is front-loaded. The second sentence about where actions live is a genuine routing hint rather than padding, though it could be folded more economically.

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 an output schema present, return values need no explanation, and a zero-parameter read-only tool has a light burden. The description is adequate, though it would be stronger if it explicitly distinguished this global rules reference from the capability catalogue and per-market action flags it references.

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 and schema coverage is trivially 100%, so the baseline is 4. There is no parameter semantics for the description to add meaning to.

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 names a specific resource (canonical protocol rules) and enumerates concrete topic areas: resolution timing, final review, bonds, fund flows, actor conditions. An agent can distinguish this static reference endpoint from market-specific siblings like problee_get_market or problee_get_market_resolution_state, though it never explicitly says 'static/reference' to contrast with per-market tools.

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?

It routes the agent elsewhere for actions ('listed in the capability catalogue and each market's action flags'), which is a partial alternative pointer, but there is no explicit when-to-call framing for the rules themselves and no stated prerequisites or exclusions relative to the many sibling get_* tools.

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