ebay_get_message

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

No annotations are present. The description fails to disclose that the tool returns a list of messages (with pagination) rather than a single message. It does not mention authentication, rate limits, or side effects. The description contradicts the schema's pagination parameters.

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 only one sentence, making it concise but insufficient. It lacks critical information about what the tool actually does and its parameters. The brevity comes at the cost of clarity and completeness.

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?

With 4 parameters (2 required) and no output schema, the description should explain the return format and how to use pagination. It provides none of this, leaving the agent to guess. The tool's behavior is poorly specified.

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 each parameter. The description adds no additional meaning beyond what the schema provides. Baseline 3 is appropriate.

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 claims to 'Get a specific message by ID', but the input schema requires conversation_id and conversation_type, and includes pagination parameters (limit, offset). This indicates the tool retrieves multiple messages from a conversation, not a single message. The description is misleading and contradicts the actual behavior.

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 sibling tools like ebay_get_conversation, ebay_search_messages, or ebay_reply_to_message. The agent must infer usage from context, which is insufficient.

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