signal_query

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

With no annotations, the description adds the cost and payment mechanism ($0.002 USDC per call via x402), which is useful behavioral context. However, it lacks disclosure about read-only nature, idempotency, or other side effects.

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 one sentence with an appended cost note, both essential. Zero waste, front-loaded purpose, every word earns its place.

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?

The description is adequate for a query tool with the filter list, but lacks explanation of the return format or pagination, which is important given no output schema.

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?

The input schema's only parameter is a generic object with an external link, so the description compensates by enumerating the intended fields (type, severity, keyword, time), adding significant meaning beyond the schema.

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 clearly states the verb 'query' and the resource 'signals' with specific filter dimensions (type, severity, keyword, time), which distinguishes it from sibling tools like 'delphi_query' or 'latest_signals'.

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 use for filtering signals but provides no explicit guidance on when to use this tool versus alternatives (e.g., 'latest_signals' or 'delphi_query'), nor any exclusion criteria.

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