Agent: fetch market signal

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

Annotations show readOnlyHint=false (write) and destructiveHint=false. The description adds 'records', confirming a write operation, but does not disclose side effects, idempotency, or other behavioral traits. With annotations already covering basic behavior, the description adds modest value.

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?

Single sentence, no wasted words. Front-loaded with the key action and resource.

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 simple record-creation tool with 4 parameters and no output schema, the description is adequate but lacks usage guidelines and deeper behavioral context. It does not clarify whether the operation is idempotent or what happens on duplicate assetId+kind.

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 has 100% coverage with minimal descriptions. The description adds examples for 'kind' (price/volume/news), providing a bit of context beyond the schema, but does not explain constraints or formats for 'value' or 'source'. Baseline 3 is appropriate due to high schema coverage.

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 'records' and resource 'market signal', with examples (price/volume/news). It clearly distinguishes from sibling tools like 'agent_execute_preapproved_order' or 'agent_flag_anomaly'.

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?

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites or context. The description merely states the action without contextual cues.

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