ebay_get_privileges

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

The description discloses required OAuth scope and mentions the returned data fields (registration status, selling limit). However, without annotations, it lacks information on rate limits, data freshness, or other behavioral aspects.

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 concise with two sentences that front-load the purpose and include essential context like OAuth scope. No redundant 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?

While there is no output schema, the description adequately summarizes the return value (privileges and selling limit). It could mention response format or pagination, but this is a simple read tool.

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 tool has no parameters, so the input schema fully covers them. The description adds no parameter info, which is acceptable; baseline for zero parameters is 4.

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 tool retrieves the seller's current set of privileges, including registration completion and selling limit details. It uses specific verbs and nouns, and is distinct from sibling tools that handle bulk operations or other specific actions.

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 implies usage for reading privileges but does not explicitly state when to use this tool over others or provide exclusions. No alternatives are mentioned.

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