mma_create_listing

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

With no annotations provided, the description carries the full burden. It discloses that the tool is free, facet-validated, and requires a specific API scope. It also specifies the third-person voice requirement. However, it does not detail the return value, error handling, or whether the operation is idempotent, leaving some behavioral gaps.

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 three sentences long, each serving a distinct purpose: stating the action, giving a prerequisite, and providing style/scope requirements. It is front-loaded and contains no filler.

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?

The description covers the prerequisite and writing style but lacks details on return values, error scenarios, rate limits, or media URL constraints. Given the tool's complexity (7 parameters, no output schema), more contextual information would be beneficial for complete understanding.

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 only 43%, meaning the description must compensate. It adds meaningful context for 'attributes' (must use facet keys from describe_catalog) and implies style for 'description'. But it does not elaborate on 'title', 'category', 'currency', or 'priceCents' beyond what the schema's constraints already imply.

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 action ('List a business, service or product') and the resource (MeetMyAgent). It distinguishes itself from sibling tools by referencing 'mma_describe_catalog' as a prerequisite, which sets it apart from other listing-related tools.

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 explicitly instructs to call 'mma_describe_catalog' first and to use only its facet keys in attributes, provides writing style guidance, and mentions the required API scope. This gives clear context for when and how to use the tool versus alternatives.

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