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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond annotations: it clarifies that this is public evidence, involves no brokerage access, no order placement, and no synthetic odds.

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, purpose front-loaded, followed by a concise safety/scope clarification. Every sentence adds value and there is no filler.

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?

The tool is simple, annotations are rich, and no output schema exists, so the description does not need to explain return values. However, it leaves both optional parameters undocumented and does not clarify filtering behavior, which is a noticeable gap for an agent trying to invoke it correctly.

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 description coverage is 0%, and the description does not mention the 'limit' or 'category' parameters at all. The parameter names are somewhat self-explanatory, but with no schema descriptions the agent receives no guidance on category values, filtering behavior, or limits beyond the raw JSON Schema constraints.

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 ('List event markets') and scopes it to Robinhood's public prediction-markets pages. It is clearly distinguishable from the singular prediction_get_market sibling, though it does not explicitly name siblings or contrast behavior.

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 states what the tool lists but gives no explicit guidance on when to use it versus prediction_get_market or prediction_rank_attention. There are no exclusions, prerequisites, or routing cues beyond the general 'public evidence' framing.

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