marketplace_search_details_create_instance

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

With no annotations, the description carries the full behavioral burden, yet it discloses nothing about authentication, side effects, idempotency, or what state the create leaves behind. The single useful hint is that the body follows a JSON:API envelope, which is a minor behavioral disclosure at best.

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?

It is short, but the path is needlessly repeated verbatim in parentheses and the sentence is not front-loaded with any meaningful purpose. There is no waste of length, but also no information density.

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 mutation tool with no annotations, no output schema, and a body schema that is an unconstrained object, the description should explain the resource being created and the required envelope. Deferring entirely to an external OpenAPI component leaves an agent unable to construct a valid call.

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% and there is only one parameter, so baseline is 3. The description does not elaborate on the body's fields; it only defers to components.schemas.MarketplaceSearchDetailCreateRequest, and the schema itself is a free-form object with additionalProperties, so the pointer adds little practical detail.

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 only restates the HTTP verb and path ('POST /v1/marketplaceSearchDetails'), which duplicates the tool name 'marketplace_search_details_create_instance'. It never says what a MarketplaceSearchDetail is or what creating one accomplishes, so an agent learns nothing beyond the already-encoded operation type.

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?

There is no guidance on when to use this tool versus siblings such as marketplace_search_details_update_instance or marketplace_search_details_delete_instance, nor any prerequisite (e.g. an existing app or merchant ID). The agent must infer the usage context entirely.

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