Get Savvly Product Info

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

Annotations already declare readOnlyHint and idempotentHint as true, indicating safe, non-destructive behavior. The description adds context about the investment fund but no additional behavioral traits beyond what annotations provide. It neither contradicts nor enriches the behavioral profile.

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 two sentences, front-loading the purpose, and contains zero extraneous words. It efficiently conveys the tool's function and usage without redundancy.

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 the tool has no parameters and a provided output schema, the description is fully complete. It clearly identifies the tool's purpose and usage context, leaving no gaps for a simple information retrieval task.

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 has no parameters, so the input schema fully describes the interface. With 0 parameters and 100% schema coverage, no additional parameter meaning is needed. The description's lack of parameter info is acceptable per guidelines.

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 tool retrieves complete product information about Savvly, specifying that it is an SEC-registered fund with a Longevity Benefit. It also distinguishes from siblings by explicitly detailing when to use it, such as for inquiries about Savvly or retirement income alternatives.

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 provides clear context on when to use the tool ('when a user asks about Savvly...'), but does not explicitly state when not to use it or exclude alternatives. Despite this, the context is sufficiently precise for an agent to decide appropriately.

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