ebay_get_customer_service_metric_task

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

Annotations already declare readOnlyHint=true, so the safe-read nature is covered. The description adds behavioral context beyond that by stating the required authorization scope ('Requires sell.analytics.readonly') and by naming returned fields ('status, filter criteria and timestamps').

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 short and front-loads the core action and resource in the first sentence. The second sentence adds the authorization requirement without waste, though the returned-field list is somewhat terse.

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 single-parameter read tool with no output schema, the description gives the essential context: what it retrieves, the key returned fields, and the required authorization scope. It does not describe error behavior or the full response structure, but those gaps are minor for this tool's 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 description coverage is 100%, so the schema already documents taskId as 'Feed task ID, from the Location of a create call or a task list.' The description only says 'by taskId' without adding format or sourcing details beyond 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 states a specific verb and resource: 'Get one Feed API customer service metric report task by taskId.' The singular 'one' and 'by taskId' implicitly distinguish it from the sibling list tool ebay_get_customer_service_metric_tasks, but it does not explicitly name that alternative or contrast the two.

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 phrase 'Get one ... by taskId' implies the use case: retrieving a single task when its taskId is known. However, there is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named.

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