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

With no annotations, the description carries the full burden and does disclose a meaningful behavioral constraint: research must be submitted first to unlock the swarm report. It does not clarify side effects, prerequisites beyond committing, or what happens if the agent has not yet submitted research.

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 description is short with no filler, but the opening phrase 'Open Future events' is ambiguous—it could be read as a verb phrase rather than the name of the event category. The commit-first caveat is buried in a second sentence that shifts focus from listing to unlocking reports.

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 tool with no annotations and no output schema, the description should clarify return value expectations, the role of the optional ticker, and the exact mechanics of the commit-first requirement. It provides some context about what Future events are but leaves critical operational details unexplained.

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 never mentions the 'ticker' parameter or how it affects results. Since there is no schema-level documentation and the description does not compensate, the agent is left without any guidance on the parameter's meaning or optionality.

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 identifies a specific resource—'Future events' as unresolved financial questions Marx collects research on—and the tool name supplies the 'list' verb. It does not explicitly distinguish itself from siblings like list_open_threads or search_feed, but the core purpose is reasonably inferable.

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 'Commit-first' instruction conveys when a user should have submitted their own research in order to unlock the swarm report, which is a form of usage guidance. However, it does not say when to prefer this tool over related siblings or when not to use it.

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