ebay_get_rate_limits

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

With no annotations, the description carries the full burden. It mentions it returns rate limit data, implying a read operation, but does not explicitly state that it is non-destructive, requires authentication, or any other behavioral traits beyond the basic functionality.

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 states the purpose and what is returned. No redundant or unnecessary information.

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 no output schema, the description explains the return values (quota, remaining calls, time until reset). It covers the main use case and the optional filters. However, it does not mention behavior when no filter is provided (e.g., returns all APIs) or any response size limitations.

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 both parameters described. The tool description does not add extra meaning to the parameters beyond the schema, so baseline 3 is appropriate. The description's mention of filtering by API name and context is already covered in 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 verb 'Get' and the resource 'application rate limits for eBay APIs', and specifies the return values (quota, remaining calls, time until reset). It is distinct from the sibling 'ebay_get_user_rate_limits' by focusing on application-level limits, but does not explicitly differentiate.

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?

No guidance is provided on when to use this tool versus alternatives like 'ebay_get_user_rate_limits', nor any prerequisites or context for usage. The description only states what it does without indications of when it is appropriate.

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