ebay_get_feed_schedule

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds non-obvious domain constraints that annotations cannot carry: schedules exist only for LMS_ORDER_REPORT, and the operation requires the sell.fulfillment scope. That is real behavioral value beyond the annotation.

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 dense sentences, front-loaded with the action and resource. No filler, no tautology, no redundancy with the schema or annotations.

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-param read with readOnlyHint and no output schema, the definition covers what the agent needs to call it correctly: what it returns, who can call it, and the only valid schedule type. The absence of output schema means return-value shape is not described, which is a minor gap but consistent with the API's idempotent read nature.

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% and the schema description already explains the scheduleId origin. The description restates that the lookup is by scheduleId and ties the ID to a specific entity type, adding a small amount of context but not exceeding what the schema provides. Baseline 3 is raised slightly because the destination-constraint sentence reinforces what the ID must reference.

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?

States a specific verb (Get) and resource (Feed API schedule) with scope (by scheduleId) and enumerates what the returned entity contains (template, trigger settings, status, last run). Immediately distinguishes it from sibling create/update/delete_feed_schedule and from ebay_get_feed_schedules (plural list).

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?

Implicitly establishes the retrieval-by-ID usage pattern, and the scheduleId schema description names the alternative sources (ebay_create_feed_schedule or a list) for obtaining an ID. Does not explicitly say when to prefer this over ebay_get_feed_schedules, but context makes the singular/plural split unambiguous.

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