ebay_validate_token_expiry

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

Without annotations, the description carries the full burden. It discloses the tool checks expiry and provides recommendations, indicating a read-like behavior. No mention of side effects or auth needs, but the behavior is straightforward for a validation function.

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, zero wasted words. It front-loads the core purpose and immediately provides specific details.

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 validation tool with no output schema, the description sufficiently explains what the tool does and its output (recommendations). Could mention return format but not necessary given simplicity.

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 each parameter described as ISO date string, Unix timestamp, or relative time. The description reinforces but does not add meaning beyond the schema's own descriptions. Baseline of 3 is appropriate.

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 validates token expiry times and provides actionable recommendations, specifying it checks if tokens are expired or expiring soon. This specific verb-resource combination distinguishes it from all sibling tools, which focus on listings, promotions, reports, etc.

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 when to use: when needing to check token expiry and get recommendations. No explicit when-not or alternatives are given, but given the sibling list contains no other token-related tool, the context is clear.

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