suppscience

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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully reveals the returned content (compared options, verdicts, purchase links), but it does not explicitly state that the operation is read-only, what happens on an invalid slug, or any other behavioral traits. 'Get' implies retrieval but is not a strong disclosure.

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 a single, well-structured sentence that front-loads the action and resource, then specifies the key return elements with zero redundancy. Every word 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?

For a simple one-parameter retrieval tool with no output schema, the description covers the main action and return contents sufficiently. Minor gaps include lack of explicit usage guidance and error behavior, but these are not critical given the tool's simplicity.

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 input schema provides 100% coverage of the single parameter, including an example and a pointer to list_guides for finding slugs. The description adds no additional parameter semantics, so the baseline score of 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 ('Get'), a resource ('one comparison guide'), and a unique identifier ('by slug'), while listing what the response contains (compared options, per-option verdicts, purchase links). This clearly distinguishes it from sibling tools like list_guides or get_supplement.

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 context is implied rather than explicit: the slug parameter description says to find it via list_guides, but the tool description itself does not state when to choose this tool over alternatives or mention exclusions. There is no clear when-to-use/when-not-to-use 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 provided, the description carries the full burden. It transparently lists the output contents but does not mention side effects, error conditions, or confirm that the operation is read-only. Since 'Get' implies read-only, it is partially transparent but omits failure modes.

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 a single sentence that packs all essential information without unnecessary detail. It lists the response contents in a compact, readable manner, and the structure is efficient.

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?

The description is fairly complete given that there is no output schema; it names all the returned elements. It lacks explicit guidance on when to use this tool relative to siblings, but the slug-based nature and the hint about search_supplements provide enough context for most use 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 schema for the single parameter 'slug' includes a clear description and an example. The tool description reinforces this by repeating 'by slug' and referencing search_supplements. Schema coverage is 100%, so the description adds marginal value beyond the schema, but the existing schema description is sufficient.

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 verb 'Get' and the resource 'supplement', and enumerates the exact contents of the response (evidence grades, dose, safety, references, purchase link, pageUrl). It is specific and distinguishes it from listing or searching tools by focusing on a single slug's full analysis.

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 implies that one should first use search_supplements to find a slug, but it does not explicitly state when to use this tool versus get_guide or list_guides. The description gives a hint but leaves the decision to inference.

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 behavioral burden. 'List' implies a read-only operation, and the topic enumeration adds useful context, but it does not describe the return format, ordering, or whether each guide contains structured data or free text. For a simple listing tool this is adequate but not rich.

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 immediately states the action and resource, then uses a compact parenthetical and colon list to enumerate content. No filler or repetition; every part adds value.

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?

This is a simple, parameterless listing tool with no output schema, so the description covers the essential purpose and scope. It might have mentioned how results are presented (e.g., titles/IDs), but the low complexity means the current description is sufficient for 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?

There are zero parameters, so the description is not required to add parameter meaning. The description's list of guide topics effectively communicates what the result set contains, which is the only relevant semantic content for this tool.

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 ('List') and clearly identifies the resource ('comparison guides'), then enumerates the exact topics included. This distinguishes it from siblings like get_guide (which presumably returns one guide) and search_supplements (which searches supplements).

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 use case evident: call this tool to see available comparison guides on specific supplement forms. It does not explicitly state when not to use it versus get_guide or search_supplements, but the enumeration of guide topics provides clear context for selection.

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 of behavioral disclosure. It does disclose the catalog size, that results include slug, evidence grade, and summary, and that it is a search operation. However, it does not describe search matching semantics (e.g., partial or exact), result ordering, or pagination behavior beyond the schema's limit parameter, leaving some behavioral gaps.

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 compact sentences with no wasted words. The primary action and scope are front-loaded in the first sentence, and the second sentence adds a clear routing instruction to a sibling tool. Every sentence 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?

For a simple search tool, this is nearly complete: all parameters are schema-documented, the returned fields are named, and the path to deeper detail via get_supplement is clear. The only minor omission is an explicit statement that results are returned as a list or array, but the field enumeration makes the response shape largely inferable.

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 input schema already documents both parameters with 100% coverage, so the baseline is 3. The description adds meaningful context by specifying that 'query' can be a name, category, or topic, which clarifies what kinds of search terms are valid. The 'limit' parameter is not elaborated in the description, but the schema already explains its default and maximum.

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 ('Search'), a defined resource ('catalog of 993 evidence-graded supplements'), and the dimensions of search ('by name, category, or topic'). It also explicitly routes users needing full analyses to the sibling get_supplement, which cleanly distinguishes this tool from its siblings.

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 usage context: use this to search the catalog and get brief matches, and it explicitly points to get_supplement for the full analysis. It does not mention all sibling tools (get_guide, list_guides) or when to avoid this tool, but the alternative guidance it provides is concrete and sufficient for the primary decision.

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