getPredictionEngineStatus

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

Annotations already mark it read-only, and the description adds valuable operational context that an unavailable engine blocks order submission and that the response exposes an 'available' field with false meaning do-not-trade. This goes beyond what the annotations alone provide.

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 first sentence is front-loaded and clear, but the description repeats the same instruction about checking before orders and not proceeding when unavailable. The 'Agent hint' section mostly duplicates the previous sentences, so the text could be trimmed without losing content.

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 zero-parameter read-only status check, the description conveys the key information: what is queried, the operational implication, and how to interpret 'available=false'. Since there is no output schema, the mention of the 'available' field is a useful behavioral detail, though a more explicit return-shape statement would be even stronger.

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?

There are zero parameters, so parameter semantics are trivial. The schema already documents this via an empty properties object, and the description does not need to elaborate.

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 states a specific verb ('Query') and resource ('prediction market matching engine') and indicates the operation is a status check. It clearly distinguishes this from sibling order-execution tools by explaining that orders cannot be submitted when the engine is unavailable.

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 gives explicit guidance on when to call: before placing any buy or sell order. It also states what to do when the engine is unavailable (inform the user and do not proceed), which functions as a clear when-not-to-trade exclusion.

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