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 behavioral burden. It discloses that listings are free, facet-validated, require a specific API scope, and must be written in third-person voice. This is substantial transparency, though it omits details like error handling or duplicate behavior.

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 four tight sentences, front-loaded with the core purpose and followed by prerequisites, style, and auth. Every sentence adds necessary information without redundancy.

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?

Given the tool's complexity (7 params, nested objects, no annotations), the description covers the essential contextual elements: prerequisites, auth scope, attribute validation, and writing style. The output schema handles return values, so no need to describe them.

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 only 43%, so the description compensates by clarifying the attributes object (must use catalog facet keys/enums) and the expected writing style for description/title. It adds critical meaning beyond the basic schema, even if it doesn't explain every parameter.

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's purpose: listing a business, service, or product on MeetMyAgent. It uses a specific verb ('List') and resource, and distinguishes from sibling tools like import or search by emphasizing 'create' context and facet-validation.

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?

It provides explicit usage guidance: call mma_describe_catalog first and use only its facet keys/enum values in attributes, plus a required API scope. It doesn't name alternatives (e.g., mma_import_listing), but the prerequisite and style instructions give clear when-to-use context.

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