site

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

With no annotations, the description carries the full burden: it does disclose the pagination cap ('Up to 50 per page') and that results are sorted and optionally stock-filtered. However, it says nothing about read-only safety, default sort order, default page, or what a returned page contains, leaving real behavioral gaps for a 5-param 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?

A single, densely packed sentence with the resource front-loaded and qualifiers trailing; no filler. It is efficient, though the compressed phrasing makes a few clauses (path or name, sorted) slightly ambiguous.

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 and no annotations means the description must cover behavior, and it only partially does: pagination, defaults, and the nature of the returned page are not specified. Adequate for a simple browse tool but missing pieces an agent would want.

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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. "A page of Decor Depot's products, optionally within a category (path or name), in stock only, sorted" conveys that this is a read operation returning a page, states the category-accepting behavior, and discloses the sort and stock constraints. However, it omits default sort ordering, pagination cursor/page behavior beyond the cap, and the shape of returned results. For a tool with zero annotations and no output schema, this is informative but incomplete.

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 concrete verb (browse/return a page) and resource (Decor Depot's products), plus scope modifiers (category, in-stock, sorted). It is clear what the tool does but never distinguishes itself from close siblings like search or filter, which could also return product listings.

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 implies a browsing/marketplace scenario via 'optionally within a category' and 'in stock only', but gives no explicit when-to-use guidance and never names search, filter, or product as the alternatives for narrower queries.

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, the description carries the full burden and does disclose two meaningful traits: the cart is scoped to this MCP session (not the store's persistent cart) and totals are live from the feed. It does not say what clear destroys, whether operations are idempotent, or how errors (e.g. invalid product) are surfaced, which matters for a mutation-capable 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?

Two tight sentences with the scoping constraint (session cart, never the store's cart) front-loaded before the action list and the checkout handoff. No filler.

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 3-parameter, no-annotation, no-output-schema tool, the description covers actions and handoff but does not describe what view returns (cart shape, totals per line) or failure behavior. Adequate but leaves an agent guessing about the return surface.

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 67%: qty and product both carry schema descriptions, while action relies on the enum alone. The description adds marginal context by mapping 'set a quantity' to the set action, but adds no detail beyond the schema, so the baseline 3 is appropriate.

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 names the exact resource (a session-scoped cart) and enumerates the full action set (add/remove/set/view/clear), so an agent knows precisely what the tool does. It also explicitly distinguishes itself from the store's own cart, which is the key ambiguity for a shopping MCP.

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?

It gives clear context for the cart's lifecycle and routes the buyer to checkout_link to complete the purchase, which is strong sibling guidance. It stops short of stating when to prefer this over alternatives like product or search for gathering item details.

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 provided, so the description carries the full behavioral burden. It does disclose the shape of the returned data (path, name, page URL, product count), which implies a read-only enumeration, but it says nothing about pagination, result size, ordering, or caching behavior 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?

Two short sentences with no filler; the resource identity and field list come first, and the usage hint follows. It is appropriately sized for a trivial no-input listing 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?

With no input schema, no output schema, and no annotations, the description is the only source of information, and it lists the concrete return fields an agent needs. It is nearly complete for such a simple tool, missing only output mechanics like ordering or pagination.

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 schema has zero parameters, so there is nothing for the description to document and the baseline of 4 applies. The mention of 'path or name' refers to how sibling tools consume this output, not to any input this tool accepts.

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 states the specific resource (the category tree Decor Depot organises products into) and enumerates the returned fields (path, name, page URL, product count), which clearly separates it from siblings like browse, product, and search. It lacks an explicit verb (list/get/retrieve), so it describes content rather than an action, slightly short of a perfect score.

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 phrase 'Use a path or a name as the category of browse' implies the intended workflow (fetch categories, then feed a path/name into browse), which is useful implied usage. However, it never states when to call this tool versus search, filter, or product, nor any prerequisite or exclusion, so guidance stays implicit.

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, the description carries the full burden and does disclose the critical trait: the server never places an order or takes a payment, so the agent must hand off rather than report a completed purchase. It also explains that multiple links can come back depending on product type. Gaps remain on auth requirements, whether links expire, and behavior with an empty cart.

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?

Front-loads the scope and the core meaning in the opening clause, then uses the closing sentence for the most important safety fact. Two sentences, no filler, though the middle enumeration of link types is dense enough to require a second read.

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-optional-param, no-annotation, no-output-schema tool, the description covers what comes back (links), the two product branches, and the non-transactional nature. It leaves only minor unknowns such as empty-cart behavior and link validity, which are not blockers to correct invocation.

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 the single optional parameter is already documented as 'one product instead of the cart'. The description restates the same cart-or-product choice without adding format or selection criteria, so baseline 3 applies.

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 resource ('the link(s) where a PERSON completes the purchase') and enumerates the two link types it can return: own-product product page/cart versus affiliate retailer buy link. The title's framing plus 'this server never places an order or takes a payment' distinguishes it from any sibling that mutates the cart, so an agent can tell it apart from cart/store without opening a schema.

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 scope is implied well ('for this session's cart (or one product)'), so an agent can infer this belongs at the end of a shopping flow, but no sibling is named and there is no explicit when-not-to-use or handoff rule. Minimum viable implied usage rather than routing guidance.

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, the description carries the full burden. It does add real behavioral detail absent from the schema — exact, case-insensitive attribute matching, price values in the store's currency, and where to discover valid attribute keys. However, it says nothing about pagination behavior, result limits, or what the response contains, which matters for a 10-parameter query 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?

One dense but front-loaded sentence that leads with the primary filter (attributes) and then price, with the examples earning their place. No filler, though the run-on structure packs four distinct concepts without separation.

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 10-parameter, unannotated tool with a nested attributes object and no output schema, the description covers the core filtering semantics well but leaves pagination, sorting, and the fulfilment enum unexplained. Adequate to select the tool, incomplete for fully informed invocation.

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 only 30%, so the description must compensate, and it does: it clarifies attribute semantics (key: value, exact, case-insensitive), the meaning of price_min/price_max in major currency units with an example, and mentions category, brand and in-stock. It omits page, page_size, sort and fulfilment, so the compensation is partial rather than complete.

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 states a specific action (filtering Decor Depot products) with named dimensions: attribute values and price range. It implicitly distinguishes itself from browse/search by emphasizing exact attribute and price filtering, but never names those siblings to make the boundary explicit.

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: it tells the agent it can combine attributes with category, brand and in-stock, and that attribute keys are the store's own specs. There is no statement of when to prefer this over search or browse, nor any exclusion or prerequisite.

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 provided, so the description carries the behavioral burden alone. It usefully scopes the payload ('everything Decor Depot publishes', listing description, price, stock, identifiers, attributes, images, buying locations), which tells the agent to expect a large read-only object, but it says nothing about errors for unresolvable ids, auth needs, 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?

One sentence, front-loaded with the resource and lookup keys before the field enumeration. The long em-dash list is dense but each item earns its place by telling the agent what data is available.

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?

There is no output schema, so the enumerated fields (description, price, stock, identifiers, attributes, images, buying locations) usefully preview the return payload for a read-only lookup. Nothing critical is missing for an agent to call it correctly, though failure behavior is unaddressed.

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 the single 'product' parameter is already documented as 'product id, product page URL, or GTIN'. The description restates the same three accepted forms without adding format examples or normalization rules, so the schema does the heavy lifting.

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 retrieval verb (implied by 'Everything Decor Depot publishes about one product') plus the resource and the three accepted lookup keys (id, URL, GTIN), then enumerates exactly what comes back. This clearly separates it from siblings like search, filter, and browse, which are multi-item tools.

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 implied rather than stated: 'one product' signals a single-item lookup versus the multi-item siblings, but no sentence says when to prefer this over search or browse, nor what happens on an unknown id. Adequate but with a clear gap.

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, the description carries the full behavioral burden. It does valuable work by disclosing the matching algorithm (all words, any order, case-insensitive) and which fields are searched, but says nothing about result shape, ordering defaults, or pagination behavior for what is clearly a paged listing.

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 dense sentence that front-loads the resource and immediately qualifies it with the matching rules. No filler, and every clause adds information an agent needs.

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 4-parameter tool with no output schema and no annotations, the description covers query semantics well but omits pagination behavior and result presentation. It is minimally sufficient, not 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?

Schema coverage is only 25% (only 'sort' is documented). The description adds meaning for the required 'query' parameter by explaining word-matching semantics, but 'page' and 'page_size' remain undocumented in both schema and description, leaving pagination behavior to guesswork.

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 names a specific resource (Decor Depot products) and precisely defines what searching means: matching against title, description, brand, category and attributes. An agent knows exactly what the tool operates on, but the description never distinguishes it from siblings like filter or browse.

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 use search versus the sibling tools 'filter' or 'browse', which are the obvious alternatives for finding products. The matching semantics suggest a keyword-search use case, but routing guidance is entirely absent.

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 provided, the description carries the full burden, and it discharges most of it by disclosing that this is a zero-argument informational lookup returning store-level facts. It does not state that it is read-only or that it has no side effects, but for a parameterless info tool the inference is safe.

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?

Two sentences, no waste: the content facets come first and the call-ordering instruction is the closing imperative. Every clause earns its place.

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 a parameterless, no-output-schema tool, the description is nearly sufficient: it enumerates what the agent will learn. It could add a note about the return shape (single object vs list of fields), but nothing essential to calling it correctly is missing.

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, so the baseline is 4. There is nothing in the schema for the description to explain or compensate for.

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 names a specific resource (the Decor Depot store) and enumerates its facets: what is sold, currency, shipping, purchase completion, catalogue size. That is far more concrete than a tautology, though it does not explicitly contrast itself with siblings like browse or categories.

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?

'Call this first' gives an explicit ordering directive that tells the agent when to invoke this over the other catalogue tools. It stops short of naming when-not-to-use or which sibling supersedes it once the overview is known.

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