relay_get_current_state

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

With no annotations, the description carries the full disclosure burden. It does add real behavioral context beyond the schema — result ordering (newest first) and the optional single-session scope — but is silent on the default limit, whether results are unbounded, and pagination or read-safety characteristics.

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?

A single tight sentence with the core behavior front-loaded and zero padding. Slightly compressed phrasing ('optionally limited to one session') costs a little precision but wastes nothing.

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?

No output schema, no annotations, and 0% schema coverage mean the description should do more. It omits the default result count, return shape, and sibling differentiation, leaving meaningful gaps for an agent invoking a retrieval 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?

Schema coverage is 0%, so the description must carry parameter meaning. It partially clarifies session_id as an optional narrow-to-one-session filter, but never explains the limit parameter (max 100, exclusive minimum 0) or what happens when it is omitted.

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?

States a specific verb (Return) and resource (most recent facts) plus ordering (newest first) and optional scoping. Clear on its own, but does not differentiate from siblings such as relay_get_context or relay_get_important_facts, so an agent must guess which retrieval tool applies.

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?

'Optionally limited to one session' hints at one usage mode but gives no when-to-use criteria and never names an alternative among the eight sibling tools. Nothing tells the agent when to prefer this over relay_get_important_facts or relay_get_context.

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