outcomes_get_event

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

No annotations are provided, so description must convey behavior. It only labels the tool as 'READ', which is insufficient; there is no mention of side effects, permissions, rate limits, or return characteristics.

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?

Description is very short but at the cost of omitting essential information. It is concise but not complete enough to be effective.

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 a single parameter and no output schema, the description still fails to explain what the event is, how responses are structured, or how this tool relates to other outcomes tools.

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 coverage is 100% with a description for eventId (事件ID). Baseline is 3 per guidelines, and the tool description adds no additional meaning beyond what the schema provides.

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?

Name 'outcomes_get_event' suggests retrieving an event, and description includes '[L:READ]' indicating a read operation. However, description is cryptic and does not clearly articulate the tool's purpose beyond the name.

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?

Only usage guidance is '请先调用 agent_catalog', implying a prerequisite but providing no when-to-use or comparison with sibling tools like outcomes_list_events or outcomes_get_market.

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