get_my_products

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

Annotations already indicate readOnlyHint=true. The description adds that it is 'Read-only,' requires an API key, and returns data shaped like 'search_products'. It does not disclose potential error conditions or side effects, but for a read-only list tool this is fairly complete.

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 well-structured with clear sections (purpose, usage, parameters, returns). It is front-loaded with the core purpose and uses an efficient number of sentences. No filler or redundant information.

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 simplicity (2 parameters, no nested objects, no output schema), the description covers parameter details, usage guidance, and return shape (by reference). It lacks information on authentication failure or error handling, but for a basic list operation this is adequate.

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 input schema has 0% description coverage, meaning the schema alone gives little meaning beyond types and default. The description compensates by explaining the api_key parameter ('Partle API key (prefix `pk_`)') and the limit parameter ('Maximum results (1–200, default 50)'), adding essential semantic value.

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: 'List products created by the API key's owner.' It uses a specific verb ('list') and resource ('products') with owner scoping. It distinguishes itself from the sibling 'search_products' by contrasting owner-scoping vs. public catalog search.

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?

Explicitly tells when to use (e.g., when user asks 'what have I listed?' or before bulk operations) and provides an alternative ('Distinct from search_products...'). This leaves no ambiguity about context.

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