ebay_get_report_metadata

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

The readOnlyHint annotation already signals this is a safe read operation, so the description does not need to restate that. The description adds no behavioral context beyond the annotation, such as what metadata is returned, whether it requires a report type, or any rate-limit considerations. With annotations covering the safety profile, a 3 is appropriate.

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, short sentence with no wasted words. It is front-loaded with the verb and resource, though it could have used the space to add differentiating detail without becoming verbose.

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 tool with no output schema and a highly ambiguous sibling name, the description is too thin. It does not explain what report metadata is, what the response contains, or how this differs from ebay_get_report_metadata_for_report_type. The two optional parameters are documented in the schema, but the overall context is incomplete.

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 description coverage is 100%, so both parameters (channel, fundingModel) are already documented in the schema. The description adds no additional meaning about how these parameters affect the metadata returned, so the baseline 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 states a specific verb and resource ('Get report metadata through the eBay Marketing API'), which is clear enough at a basic level. However, it does not distinguish this from the sibling ebay_get_report_metadata_for_report_type, which sounds nearly identical, so an agent could pick the wrong one without deeper investigation.

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 given about when to use this tool versus ebay_get_report_metadata_for_report_type or ebay_get_report. The description only names the API, not the conditions or alternatives, so the agent is left to infer usage from the name and schema.

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