list_signals

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

Annotations declare readOnlyHint=true and destructiveHint=false, covering safety profile. Description adds valuable context about what constitutes signals (external feedback examples) but omits behavioral details like pagination behavior, rate limits, or default sorting. No contradiction with annotations.

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 well-structured sentence with zero waste. Front-loaded with verb and resource ('List signals'), immediately clarifies domain with examples in parentheses, and ends with capability note ('with optional filters').

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?

Adequate for a 6-parameter read-only list operation with robust schema coverage and annotations present. However, lacking output schema, the description omits what the tool returns (e.g., array of signal objects) and pagination behavior details that would complete the picture.

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 baseline is 3. Description mentions 'optional filters' generally corresponding to the filter parameters (ideaId, source, sentiment, category) but does not add semantic details, validation rules, or format specifics beyond what the schema already provides.

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?

Clear verb 'List' + resource 'signals' with helpful parenthetical examples distinguishing what signals are (Twitter, Reddit, support tickets). Implicitly distinguishes from sibling 'get_signal_analytics' (list vs. analytics) and 'attach_signal' (retrieval vs. attachment), though explicit sibling differentiation would strengthen it.

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?

States 'with optional filters' implying filter capability exists, but provides no explicit guidance on when to use this tool versus alternatives like 'get_signal_analytics' or when filtering is necessary versus fetching all signals.

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