get_my_listing

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

With no annotations provided, the description carries the full behavioral disclosure burden. It discloses that the operation covers this account's own listings, includes any publish_status such as draft, and returns detailed fields like roles, category, rich_context, outbound_tier, and reputation. The 'Get' verb makes the read-only nature clear, and no contradiction is present.

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, focused sentence that front-loads the core purpose and then enumerates the valuable return fields. Every clause contributes meaning, with no filler or redundant restatement of the tool name.

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 low-complexity tool with zero required parameters and no output schema, the description provides sufficient context: what it retrieves, from whose account, and what statuses are included. It lacks explicit error or output-shape details, but the listed fields and 'full detail' phrasing make the tool adequately complete for an agent.

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 only parameter, listing_id, is fully documented in the schema with its optionality and default behavior, so the schema already provides 100% coverage. The description adds context by framing the tool as operating on the account's own listings, but does not add additional parameter-level detail beyond what the schema states.

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 ('Get'), a resource ('one of this account's own listings'), and the level of detail ('full detail'), which clearly distinguishes it from sibling list_my_listings. It also conveys the inclusion of any publish_status, including draft, making the tool's scope unambiguous.

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 clearly implies the tool is for fetching detailed data about the account's own listing, including drafts, which differentiates it from search_directory or list_my_listings. It does not explicitly state when not to use it or name alternatives, but the context is clear enough for an agent to route correctly.

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