Orbylon

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond the annotations: these tokens are closed-loop, non-cash, non-transferable, and the issuer is named in the answer.

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 sentences with no filler. The core action is front-loaded, the input is stated in the second sentence, and the final sentence adds an important restriction without bloating the description.

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-only lookup tool with strong annotations and no output schema, the description is complete enough. It explains what is returned ('what is left'), the token scope, and that the issuing business appears in the answer.

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%, with the 'code' parameter already explained via an example ('ABCD-2345-PQRS'). The description only restates that the tool takes 'the code printed on the card,' adding minimal semantic value beyond the schema.

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 verb ('Return what is left') on a specific resource ('closed-loop token issued by a business through Orbylon') and enumerates the token types it covers: gift card, prepaid hours, membership, or points balance. This clearly distinguishes it from siblings like lookup_business or place_order.

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 makes the triggering condition clear: use this when you have a code printed on a card and need to know its remaining value. It does not explicitly list when-not-to-use scenarios or name alternatives, but the resource and purpose are unambiguous enough for an agent to select it correctly.

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?

Annotations already mark the tool as read-only and idempotent, and the description adds significant context: returned URLs return HTTP 402 with payment terms, payment settles to the business, and failed calls are not charged. This goes well beyond the structured annotations.

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 dense sentences with no filler. The return fields are front-loaded, and the important payment-behavior caveat is stated compactly without repeating the tool name or title.

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?

Even with no output schema, the description enumerates the returned fields and explains the behavioral semantics of those returned endpoints, including the 402 response and no-charge-on-failure guarantee. For a one-parameter read-only listing tool, this is 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?

The single domain parameter is already fully described in the input schema with a concrete example, and the description adds no additional parameter-level meaning. With 100% schema coverage, 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 uses a specific verb ('Return') and a specific resource ('priced endpoints a verified business publishes'), and it names the exact fields returned. This clearly distinguishes it from sibling listing tools like list_business_offerings and list_verified_businesses.

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 purpose is obvious, but the description does not explicitly state when to choose this tool over alternatives or when not to use it. The distinction from list_business_offerings is implied rather than 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?

Annotations already declare readOnlyHint=true and idempotentHint=true, covering safety. The description adds valuable behavioral context by explaining the semantics of a negative result: 'A not verified answer means Orbylon has no proof about them, not that they are fraudulent.' It also discloses what the record contains, enriching the agent's understanding beyond the structured annotations. No contradictions.

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 front-loaded with the main return value, then provides usage guidance, then clarifies negative-result semantics. Each sentence earns its place, though it is slightly longer than strictly necessary. 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?

Given there is no output schema, the description does an excellent job of explaining what the tool returns: the domain-bound Ed25519 public key, verification time/method, and provable capabilities (signed documents, catalogue). It also clarifies the meaning of not-verified results. With only one simple parameter and rich behavioral disclosure, nothing essential 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?

Schema description coverage is 100% and the single 'domain' parameter already has a description with an example. The description repeats the domain concept but adds no new format, validation, or usage details beyond the schema. 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 states a specific verb ('Return') and resource ('verified identity record for a domain'), and enumerates the contents of the record (Ed25519 public key, verification timing/method, provable capabilities). This clearly distinguishes it from sibling tools like list_verified_businesses (which lists many) and check_business_token (which presumably checks a token rather than looking up a domain).

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 gives an explicit when-to-use directive: 'Use this before trusting or transacting with a business.' This is strong contextual guidance. It does not name alternatives or state when not to use it, so it misses the top tier for explicit when-not/alternatives, but the guidance is clear and actionable.

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?

Annotations only indicate readOnlyHint=false and idempotentHint=false, so the description carries the behavioral burden. It richly discloses what happens: the order goes straight to the business, returns a reference and status URL, conditionally returns pay_url or book_url, and explicitly states money goes to the business and never to Orbylon. This goes well beyond the basic mutation hint.

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 compact yet dense, with the primary action and prerequisite front-loaded in the first sentence. Every subsequent sentence adds a distinct behavioral fact—routing, return values, payment handling, and appointment flow—with no filler or repetition of schema content.

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, the description correctly takes responsibility for explaining return values, and it does: a reference, status URL, conditional pay_url, and book_url. It also covers the key trust-related behavior (money goes to the business) and the prerequisite link to list_business_offerings, making the tool safe for an agent to invoke without guessing.

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 71%, so most parameters are already documented in the schema. The description adds useful context about domain verification and the meaning of pay_url/book_url, but it does not materially explain the selection between item and item_id, or the fulfilment object's requirements beyond what the schema already states. It is adequate but does not compensate significantly for the undocumented parameters.

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 opens with a specific verb-resource pair: 'Place an order for an item a verified business publishes', and immediately links to the sibling tool list_business_offerings for sourcing items. It clearly distinguishes this from the other business-list/readiness tools by framing it as the transactional ordering 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?

The description gives clear context: it is used after a verified business publishes an offering, and directs the agent to list_business_offerings for the item source. It does not explicitly state when not to use this tool, but the direct reference to the prerequisite and the contrast with the read-only sibling tools makes the usage scenario fairly unambiguous.

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?

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=false, non-destructive) but the description adds real value beyond them: the request is emailed to a third party, the business replies directly to the customer, no payment or wallet is involved, and consent gates the disclosure of personal data. It also discloses the return shape (reference + status URL), which matters since no output schema exists.

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?

Four short sentences, front-loaded with the purpose and the eligibility condition, followed by the mechanics (email, reply), the cost/consent constraints, and the return value. Every sentence carries information; 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 12-parameter, 6-required external-communication tool with no output schema, the description covers the critical unknowns: eligibility, third-party data flow, consent requirement, no payment, and the return value. Minor gaps remain, such as idempotency/retry behavior and what happens on a rejected request.

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 all 12 parameters, including consent, email/phone, and item semantics, are already documented in the schema. The description restates the consent rule and the price_on_request constraint on item but adds no syntax or format guidance beyond that, 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 verb+resource ('Ask a verified business for a quote') and narrows it to items flagged price_on_request: true, with concrete examples (roofer, lawyer, garage). This distinguishes it from siblings like place_order (which handles priced items) and list_business_offerings (the catalogue it reads from).

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?

Gives a clear precondition for use — the item must be price_on_request in list_business_offerings — and notes nothing is paid or owed, implicitly steering priced purchases to place_order. However, it never names the alternative tool explicitly nor states an explicit when-not-to-use case.

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