ProfitShop

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

With no annotations supplied, the description carries the full behavioral burden. It discloses that the data returned is current pricing/availability plus the full description, implying a read-only lookup, but says nothing about failure behavior for invalid ids, currency/locale of prices, or rate limits.

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?

A single front-loaded sentence with the verb, resource, returned fields, and id provenance all in place; every clause earns its spot and nothing is padded.

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 one-parameter read tool with no output schema, the description covers the key gaps: what is returned and where the identifier comes from. Only edge-case behavior (unknown id, availability semantics) is left unaddressed, which is minor at this complexity.

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 100% and the schema already gives the example format, so the baseline applies. The description still adds genuine meaning by naming search_products as the source of valid product_id values, provenance the schema does not convey.

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?

States a specific verb and resource ("Get ... one ProfitShop product") and enumerates the returned fields (price, availability, full description), which distinguishes it from the sibling search_products that returns lists rather than a single full record.

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 parenthetical "(from search_products, e.g. K382-19120)" makes the intended workflow explicit: use search_products to obtain an id, then call this tool. It stops short of stating exclusions, such as what to do for bulk lookups or when the id is unknown.

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

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose the return payload (price in EUR, stock status, product URL, image) plus multilingual query support. It says nothing about result ordering, rate limits, authentication, or behavior when no matches are found, which are the gaps that matter for an unannotated tool.

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 core capability is correctly front-loaded in the first sentence. The second sentence, however, mixes useful scope (product categories, bilingual queries) with marketing filler ('by GETA Hellas (since 1999)') that consumes space without helping the agent invoke the tool.

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?

No output schema exists, so the description's return-field summary is genuinely necessary and it delivers it. All four parameters are documented and the tool is a simple flat search, so the remaining omissions (ordering, empty-result behavior) are minor for this complexity level.

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%, so page, query, max_results and in_stock_only are already documented in the schema, making 3 the baseline. The description adds only marginal parameter meaning through 'Works in Greek or English' (implying query accepts either language) and the price-in-EUR framing; it does not clarify paging behavior or how in_stock_only interacts with max_results.

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 gives a specific verb+resource ('Search the ProfitShop product catalog') and names the concrete store and domain, so an agent knows exactly what is being queried. It never mentions the siblings get_product or store_info, so the distinction between searching and fetching a single product is left implicit rather than stated.

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?

Usage is only implied: the agent must infer that this is the entry point for product discovery and that get_product handles detail lookups. The one genuinely useful usage hint is 'Works in Greek or English', which tells the agent either language is acceptable for the query, but there are no when-not conditions or named alternatives.

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

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

No annotations are supplied, so the description carries the full behavioral burden and discloses almost nothing: it does not say whether this performs a lookup, whether the content is static or live per-store configuration, whether any auth/context is required, or what a caller receives. Only the implied read-only framing can be inferred from the topic-list phrasing.

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 a single short fragment with no filler, so nothing is wasted, but it is under-specified rather than concise: a leading verb and an object (e.g. 'Returns ProfitShop store details covering...') would cost two words and remove the ambiguity. Front-loading is fine since there is only one clause.

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 zero-argument lookup, the topic list gives an agent a reasonable sense of what topics the response covers. However, with no output schema and no annotations, the description should say what the call actually returns (a store-info object? a single string per topic?) and is silent on that.

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 tool takes zero parameters and the schema is empty but open (additionalProperties: true), so there is nothing for the description to disambiguate. Per the zero-parameter baseline, no gap is held against it here.

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 is a noun-phrase topic list ("shipping, payment methods, returns, contact details") with no verb, so it only implies retrieval of ProfitShop store information rather than stating it. The subject areas are specific enough to guess the resource, and the 'store_info' name plus the sibling list (get_product, search_products) makes the broad domain clear, but an agent must infer the action.

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 statement of when to call this versus anything else, no prerequisites, and no exclusions. The sibling tools are product-oriented, so overlap is unlikely and the lack of routing guidance is less damaging, but nothing in the text helps an agent decide to use it.

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