read_signals

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

Annotations already mark it as readOnlyHint=true and destructiveHint=false, indicating safe read operations. The description adds value by explaining the two modes of operation and that signal IDs are returned for replying, which goes beyond the 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?

The description is two sentences, concise, and front-loaded. It efficiently conveys the tool's purpose and behavior without unnecessary 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?

Given only one optional parameter, no output schema, and adequate annotations, the description is mostly complete. It explains the dual mode operation and the purpose of the returned IDs. The lack of explicit return format is acceptable for a simple read tool.

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?

There is only one parameter with 100% schema description coverage. The description clarifies the two behaviors (summary vs. threaded) and mentions the IDs for replying, adding context beyond the schema's description. This helps the agent decide how to use the slug.

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 it reads community responses to articles and distinguishes between a summary mode (when slug omitted) and a threaded mode (when slug provided). This differentiates it from sibling tools like read_interview which read different resources.

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 explains what the tool does and how the optional slug parameter changes behavior, but it does not explicitly state when to use this tool versus alternatives like send_signal or read_interview. The hint about replying with send_signal is helpful but not comprehensive guidance.

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