Aguasto Research

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds genuinely new behavioral context by enumerating exactly what is returned (description, date, canonical URL, Markdown link) and ruling out article body retrieval, which prevents an agent from misusing this as a content fetch.

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, zero filler. The positive capability is front-loaded and the scope exclusion immediately follows, which is exactly the right order for an agent scanning for fit.

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 compensates well by naming the returned fields. What's missing is failure behavior (unpublished, renamed, or nonexistent path) for a lookup keyed on an exact path — a reasonable but not critical gap for a simple read tool.

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%; the single `path` parameter is documented in-schema with concrete examples (/gpus, /company). The description adds nothing about the path format — e.g., whether published paths can change or what happens on an unknown path — so the baseline of 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 (retrieve) and a precisely delimited resource (a published page's metadata fields), and explicitly caps the scope with 'Not the full article text.' The distinction from search_pages is inferable (single page by exact path vs. search) but never named.

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 negative guidance ('Not the full article text') tells the agent what this tool won't give, which is useful. But it never names an alternative for full content, nor says to use search_pages when the exact path is unknown — the main routing decision for this tool family is left 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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context: results are limited to published pages and only include titles/descriptions/canonical refs rather than full body content. It says nothing about result volume or what happens when nothing matches.

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, front-loaded with the result shape before the follow-up pointer. 'Follow the page for full sourced evidence' is slightly promotional phrasing but still carries routing information, so little 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, the description does the minimum by naming the returned fields (titles, descriptions, canonical references). It leaves open query syntax, the meaning/default of limit, and behavior on empty results — enough gaps that an agent is guessing on invocation 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?

Schema description coverage is 0%, so both parameters rest entirely on the description, which says nothing about what 'query' accepts (free text? phrase? max 2000 chars?) or what 'limit' defaults to. With no compensation for a zero-coverage schema, this is a clear 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 ('Find') and resource ('published Aguasto page titles, descriptions and canonical references'), which tells an agent exactly what comes back. The closing line hints that this is a lightweight discovery step distinct from get_page, though it never names the sibling.

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?

'Follow the page for full sourced evidence' implies that this tool is for discovery and that get_page is for full content, but the alternative is never named and no when-not-to-use condition is given. Usage is inferable rather than stated.

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