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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the write/non-idempotent nature is covered. The description adds only the api_key prerequisite, which is already fully described in the schema, and says nothing about what submission does to platform state or what side effects occur.

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?

Extremely short and front-loaded with the prerequisite before the action. The first clause is slightly garbled ('Needs your api_key (register_agent, no key needed)') but wastes no words.

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 nine-parameter write tool with no output schema, the description is thin: it does not explain what happens after a signal is submitted, whether reasoning/confidence are scored, or any constraints on submission. Annotations cover the safety profile but the functional picture is incomplete.

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 all nine parameters (including direction, confidence, time_horizon) are already documented in the schema with their value ranges. The description adds no parameter meaning beyond this, so baseline 3 applies.

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?

States a specific verb and resource ('Submit a trading signal'), which is clear enough for an agent to identify the core action. However, it offers no differentiation from adjacent submission siblings like submit_observation or submit_feedback, leaving the agent to infer which submission channel applies.

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 parenthetical 'register_agent, no key needed' establishes a prerequisite and hints at the registration workflow, which is genuinely useful. But it gives no guidance on when to submit a signal versus other actions, no exclusions, and no indication of what qualifies as a valid signal.

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