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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered without the description. The description adds nothing behavioral beyond the annotations -- no note on whether state is cached, how fresh the deadline/trading-end values are, or any latency/auth caveats. It only enumerates return fields, which the output schema already provides.

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?

One short sentence with zero filler and the key information front-loaded. It is appropriately sized for the tool, though the bare field list style leaves it feeling more like a schema echo than an orientation sentence.

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?

An output schema exists, so return values need not be re-explained, but the description still omits parameter guidance in the face of 0% schema coverage and gives no basis for choosing this tool over the several sibling market-state/read tools. For a tool in a crowded family, this is too thin to route an agent reliably.

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% for both parameters, so the description should carry the burden of explaining marketAddress and chainId. It mentions neither: there is no indication of the identifier format, or that chainId is optional and what the default chain is. The description therefore leaves the parameters entirely undocumented.

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 gives a clear verb ("Get") and names the specific state fields returned (marketState, lifecycleStage, stageDeadline, tradingEndsAt, outcome), which conveys the resource's nature. However, it reads as a field dump rather than a purpose statement and does nothing to distinguish it from near-neighbors like problee_get_market or problee_get_market_resolution_state, which an agent could easily confuse it with.

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 no when-to-use guidance, no condition under which this tool is preferred, and no mention of the overlapping siblings (get_market, get_market_resolution_state) that would be the natural alternatives. The agent is left to infer the choice entirely.

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