get_marketplace

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

With no annotations, the description must disclose behavior. It mentions pagination and filtering but does not specify side effects, rate limits, or whether results are cached. However, the tool is a read operation, so the description is mostly adequate.

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 concise (two sentences), front-loaded with the purpose, and lists features efficiently without unnecessary words.

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 8 parameters and no output schema, the description covers all parameter features but omits details like default limit (1000), maximum limit, or response structure. It is sufficient for basic use but could be more complete.

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 description maps all 8 parameters to their roles (start/limit for pagination, query for search, tlds for filtering, sld_length_min/max for length filters, sort_name/sort_direction for sorting), providing full semantics despite 0% schema coverage.

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 verb 'browse' and resource 'domains listed for sale on the Porkbun marketplace', making the tool's purpose distinct from siblings which focus on domain management or other operations.

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 lists supported features like pagination and filtering but does not provide explicit guidance on when to use this tool versus alternatives or mention prerequisites. Since there are no sibling marketplace tools, the lack of alternatives is mitigated, but no usage context beyond features is given.

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