tickory_list_relay_events

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

No annotations are provided, so the description must fully convey behavioral traits. It suggests a read operation ('list') but does not explicitly state idempotency, rate limits, authentication needs, or the meaning of 'recent'. The scope is limited to one source, but details like pagination or ordering are missing.

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 a single, well-structured sentence that efficiently conveys the tool's purpose, target, and output characteristics. Every word adds value, and the most critical information is front-loaded.

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 the presence of an output schema (not shown), the description adequately covers the tool's behavior. It mentions the output includes 'per-route summary status', which aligns with typical event listing tools. However, details like default limit, sorting order, or event recency definition would improve completeness.

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 coverage is 100% with clear descriptions for both parameters. The description adds context about the events being inbound and recent, and includes the per-route summary status, which helps understand the output but does not provide additional parameter-specific details 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 tool lists recent inbound relay events for a specific TradingView source, and includes the key output feature (per-route summary status). It effectively distinguishes from siblings like tickory_list_relay_sources (lists sources) and tickory_get_relay_trace (trace of a single event).

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 usage for viewing events from a source, but provides no explicit guidance on when to use this tool versus alternatives (e.g., tickory_get_relay_trace for detailed trace) or when not to use it. No exclusions or prerequisites are mentioned.

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