closing_soon

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds useful behavioral context beyond annotations: it scopes results to both venues and indicates ordering by volume, giving the agent a clear model of what the tool returns.

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?

A single, front-loaded sentence with no filler. Every phrase conveys meaning, and the dash clause adds useful context about why volume matters without bloating the description.

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?

For a simple query tool with rich annotations and only three optional parameters, the description covers the core semantics: time window, venue scope, and ordering. The limit parameter is left implicit, and there is no output schema, but the defaults in the schema mitigate the gap.

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%, so the description must compensate. It does clarify 'hours' via 'within N hours' and 'venues' via 'either venue', but 'limit' is never explained and no parameter names are explicitly connected to their meanings. The 'by volume' clause partially clarifies ordering but not the limit parameter.

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 the resource ('markets closing within N hours') and the selection/sort criterion ('by volume'). It is specific enough to distinguish the tool from broad search tools, though it does not explicitly name a sibling or state 'list/find' as the verb.

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 context is implied: use this when you want markets that are closing soon and sorted by trading activity. However, there is no explicit guidance about when not to use it or which sibling tools (e.g., find_markets, search_markets) are better suited for other discovery needs.

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