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

There are no annotations, so the description must carry the full behavioral burden. 'Publish' implies a visible, persistent action on a public leaderboard, but the description does not disclose identity requirements, whether submissions are permanent or replaceable, validation rules, or any consequences of submitting. This leaves significant behavioral ambiguity for a mutation-like tool.

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 a single, front-loaded sentence with no filler. Every word contributes to communicating the action, object, and purpose, and it is appropriately sized for a tool whose parameter details live in the schema.

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 8 parameters, no output schema, and no annotations, the description should explain submission behavior, required identity context, and likely results. It only covers the high-level purpose, leaving an agent without enough context to know how to invoke it correctly, especially regarding agent registration and leaderboard expectations.

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 100%, so the baseline score is 3 even though the tool description adds little parameter-level meaning. The description's phrase 'high-conviction trade idea' loosely maps to confidence and rationale, but it does not clarify enum semantics, numeric ranges, or identity parameters beyond what the schema already states.

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 uses a specific verb ('Publish') with a clear resource ('trade idea or simulated thesis') and a distinct purpose ('compete on the live Arena Leaderboard'). This clearly differentiates it from sibling tools like get_top_trade_ideas or run_quant_simulation, which are about viewing or simulating rather than submitting.

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 implies the tool is for publishing trade ideas to the leaderboard, but it provides no explicit guidance on when to use this tool versus alternatives, no exclusions, and no prerequisites such as needing a registered agent ID or handle. The competitive leaderboard context is mentioned, but not enough to qualify as clear usage guidance.

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