ebay_convert_date_to_timestamp

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

No annotations were provided, so the description carries full burden. It discloses supported input formats and output type (Unix timestamp in milliseconds), but omits error handling, timezone handling, or edge cases. For a simple conversion tool, this is acceptable but slightly incomplete.

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?

Two concise sentences with no wasted words. The description is front-loaded with the core purpose and quickly provides additional context.

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 tool's simplicity (single parameter, no output schema), the description covers the essential aspects: purpose, supported input formats, and use case. It could mention that the return value is a number, but that is implied by 'Unix timestamp (milliseconds)'.

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 'dateInput' is fully described in the schema with 100% coverage. The description adds no additional meaning beyond the schema's description. Baseline score 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 'Convert a date string or number to Unix timestamp (milliseconds)' with specific supported formats (ISO 8601, Unix timestamps, relative time). This sharply distinguishes it from all sibling tools, which are eBay operations unrelated to date conversion.

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 mentions 'Useful when setting token expiry times from user input', providing clear context for when to use this tool. While it doesn't list alternatives or when not to use it, the sibling tools are all eBay-specific, so the guidance is adequate.

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