Ace Website MCP

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

With no annotations, the description carries the full burden. It usefully discloses a return value (continue_url) and a key behavioral fact ('does not charge anything'), but omits auth requirements, idempotency, and expiry behavior of the checkout session.

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?

Three short, front-loaded sentences with no filler; the primary action, next-step instruction, and safety note all earn their 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?

For a tool with no output schema, the description adequately explains the returned continue_url and that no charge occurs. However, it leaves the offer_id/quantity semantics and any auth or session-lifetime context unexplained.

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 0% for two parameters. The description alludes to 'one offer' (mapping loosely to offer_id) but says nothing about quantity, and the enum values are only self-documenting via the schema. It does not compensate for the coverage gap.

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+resource (start a purchase of one offer) and distinguishes itself implicitly from get_checkout by being the creation step. It doesn't explicitly name siblings, but the action is unambiguous.

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 the workflow ('send the buyer there to pay') but never explicitly states when to use this versus get_checkout or how it fits the purchase flow. Usage context is inferred rather than declared.

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 burden. 'Read' weakly implies a non-mutating operation, but the description says nothing about required authentication, error or expiry behavior, or whether the checkout is retrieved as a live or frozen snapshot.

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 well-formed sentence with zero filler, and the resource is front-loaded after the verb. It is arguably over-terse for a tool whose domain is ambiguous, but nothing in it is wasted.

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 with no output schema and no annotations, the definition is minimally adequate: it establishes the lookup key and the relationship to create_checkout. It omits the return shape, error semantics, and id format, which an agent would need to use it confidently.

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 0% and the single parameter 'checkout_id' is a bare string with no description. The tool description adds no format, provenance, or validity information (e.g. whether the id comes from create_checkout's response), so the agent must guess the parameter's shape.

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 ('Read') and resource ('checkout'), and explicitly ties the tool to its sibling 'create_checkout', which helps an agent place it in the lifecycle. It stops short of 5 because it never clarifies what a 'checkout' represents in this domain (order? cart? grant?), so the resource remains somewhat abstract.

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: the phrase 'started with create_checkout' signals that this tool is the read counterpart to a creation flow. There is no explicit when-to-use, no exclusions, and no guidance on what to do if the checkout does not exist or is expired.

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 useful behavioral content: prices are Stripe-verified and availability is live, which tells the agent the data is authoritative and current. However, it says nothing about read-only nature, authentication, rate limits, or pagination, so meaningful gaps remain.

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 no filler. The scope ('everything an agent can buy') comes first and the value-added return details follow, so 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?

There is no output schema, so the description must carry return-value meaning, and it does by naming prices, billing terms, delivery, and availability. It is nearly complete for a zero-parameter list tool, missing only format/pagination/auth details.

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 per the rubric the baseline is 4. There is no parameter syntax or filtering behavior the description could clarify, and it does not attempt to invent any.

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 clear resource ('Everything an agent can buy from Ace') and enumerates the content returned (Stripe-verified prices, billing terms, delivery, live availability). It is distinguishable from checkout and page-reading siblings, but never uses an explicit listing verb or names what it is not.

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 explicit when-to-use guidance and no mention of alternatives such as create_checkout, get_checkout, or search_pages. The only implied usage ('everything an agent can buy') is that it is a catalog browse step, but nothing routes the agent between this tool and its siblings.

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 it does disclose useful traits: the Markdown-for-Agents conversion path, a fallback stripped-text mode, and a hard 40,000-character cap. It says nothing about permissions, error behavior for off-domain or unreachable URLs, or redirect handling, so material gaps remain.

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 action and scope, with no redundant or filler content. Every clause (domain, format, size cap) adds decision-relevant 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?

For a one-parameter retrieval tool with no output schema and no annotations, the description covers output format, size limit, and domain scope, which is nearly everything needed to call it correctly. Only failure/error semantics are absent.

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 0% for the single url parameter, so the description must compensate. It does add real meaning by constraining the target to https://ace-bl.tech pages, but it does not clarify path syntax, query-string handling, or whether non-domain URLs are rejected.

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 (Read) and resource (one https://ace-bl.tech page) plus the output format, so the agent can distinguish it from search_pages which handles multi-page queries. It stops short of explicitly naming the sibling it is not, so it is clear but not fully differentiated.

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 'one ... page' implicitly contrasts with search_pages for multi-result queries, but there is no explicit when-to-use, when-not-to-use, or named alternative. Usage is inferable but not stated.

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 burden. It usefully discloses the search corpus (URL paths from the sitemap, not page body text) and the return shape (URLs plus match score). It says nothing about pagination via limit, result ordering, rate limits, or failure behavior.

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 the search mechanism front-loaded and the return value second. No filler or redundant restatement of the tool name.

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 two-parameter read-style search with no annotations and no output schema, the description covers the essential unknown: what is searched (URL paths) and what comes back (URLs with scores). The omission of limit behavior and any notion of result set size keeps it from being fully 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 description coverage is 0%, so the description must compensate. It clarifies that the query matches words in a page's URL path, which is genuine added meaning over a bare 'query: string'. The limit parameter (1-50, default 20) is never explained or even acknowledged.

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 (Find) and resource (pages) plus the exact search mechanism: words in the URL path via sitemap search. This is more precise than a generic 'search pages' and implicitly separates it from read_page, though it does not name any sibling explicitly.

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 by the search scope ('by words in their URL path (sitemap search)'), which tells the agent this is a URL/sitemap lookup rather than content search. However, there is no explicit when-to-use, when-not-to-use, or alternative such as read_page for fetching an actual page.

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 disclose the kind of content returned (sitemap, docs, contact, discovery documents) and implies a read-only, zero-parameter call, but says nothing about auth requirements, rate limits, or response format.

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 no filler; the site identity and returned links are packed efficiently. Slightly awkward phrasing around the link list, but nothing is wasted.

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 output schema and no annotations, the description is the only source of information about the return value. It names the categories of links returned, which is helpful, but does not describe the response shape or how the discovery documents are structured, leaving a modest gap for an agent that needs to consume the output.

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 there is nothing for the description to disambiguate; baseline 4 applies. No parameter claims are made that could mislead.

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 resource (the Ace site at ace-bl.tech) and what it returns (sitemap, docs, contact, discovery documents), which distinguishes it from all five siblings that deal with checkouts, products, or page content. It lacks an explicit verb like 'get' or 'list', but the informational intent is unambiguous.

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 tool versus alternatives such as read_page or search_pages. The agent must infer it is a discovery/entry-point tool; no conditions, prerequisites, or exclusions are given.

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