get_products

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

With no annotations, the description carries the burden of disclosing behavior. It states the read-only nature ('Get rows') and describes the filtering mechanism and default behavior of returning all rows when filters is empty. It does not describe return format or error handling, but the presence of an output schema covers return structure.

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 two concise sentences with no redundant information. It front-loads the core purpose ('Get rows from products') and immediately follows with the parameter semantics.

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 simple read tool with one optional parameter and an output schema, the description sufficiently covers purpose, filter usage, and default behavior. It lacks details on edge cases like invalid JSON or pagination, but these are not essential for correct invocation in most cases.

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 fully explains the only parameter, 'filters', providing a JSON format example and the meaning of an empty string. This is critical since the schema provides no description for this parameter, and the tool-level description compensates thoroughly.

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 retrieves rows from the 'products' resource, using a specific verb ('Get') and resource name. This distinguishes it from siblings like get_users and get_orders, which target different resources.

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 explains how to use the filters parameter (JSON string format and empty string for all rows), but it does not explicitly discuss when to use this tool versus alternatives or mention any exclusions. Usage is implied by the tool name and resource, but no explicit comparison to siblings is provided.

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