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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses the authentication requirement, explains why anonymous callers cannot use it, and states that results are scoped to the caller's own filed requests. It does not explicitly say the call is read-only or describe side effects, but for a list operation the most important behavioral risks are covered.

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 compact: two sentences, with the core resource and ordering front-loaded and the auth caveat following immediately. The 'INFLUENCE —' prefix is cryptic and adds little for an agent, but it does not create meaningful bloat.

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?

For a simple list operation with one optional parameter and no output schema, the description covers the return scope, ordering, authentication prerequisite, and anonymous fallback. The context parameter is already fully explained in the schema, so nothing essential is missing.

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 only parameter, 'context', is fully documented in the schema with 100% coverage, including its optionality, one-sentence expectation, and the fact that it is never included or used for ranking. The description adds no parameter-specific information, so the baseline score of 3 applies.

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 names the resource ('check requests you filed'), the ordering ('newest first'), and clearly distinguishes this from reading a single request via check_status. The word 'list' in the auth note removes any ambiguity about the operation. It is immediately clear what the tool returns and how it differs from related tools.

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 explicitly states when the tool is usable ('Requires a key or login') and gives the alternative for anonymous callers: 'should read a single request with check_status instead.' This is direct, actionable routing guidance rather than an implied usage hint.

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