get_top_rates

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

With no annotations provided, the description carries the transparency burden. It does disclose that results include 'freshness and attribution metadata', which is useful, and the verb 'Return' implies a read-only operation. However, it does not explain ordering, default limit behavior, or what qualifies as a 'supported category', which would make the behavior fully transparent.

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 focused sentence with no filler. It front-loads the core action and result, then appends the metadata detail, making it easy to parse quickly.

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 annotations and no output schema, this description is too thin for full standalone understanding. It does not enumerate supported categories, define 'top' ranking criteria, mention the default limit, or distinguish its behavior from closely related sibling tools.

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?

Only 50% of parameters are described in the schema (category has examples, limit does not). The description adds minimal meaning for category by framing it as 'supported category', but provides no semantic detail for limit, such as whether it controls the number of returned rates or how truncation works.

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 identifies a specific verb ('Return'), resource ('top SwitchWize rates'), and scope ('for a supported category'), which is clear and actionable. It does not explicitly compare against sibling tools like get_top_hysa_rates, but the category-driven scope gives reasonable differentiation.

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 no guidance about when to use this tool versus siblings such as get_top_hysa_rates or get_rate_freshness. It does not state exclusions, fallback conditions, or scenarios where another tool would be preferable, leaving selection to inference.

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