getYearnVaultInfo

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

No annotations provided, so description must fully disclose behavior. It says 'Get detailed information' without specifying what fields or structure are returned, whether it is a read-only operation, or any potential performance implications. Lacks essential behavioral context for an agent.

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 concise sentence that conveys the primary purpose. No extraneous words. However, it could be slightly improved by adding structure or clarifying what 'detailed information' includes, but it remains 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?

Lacks output schema and does not describe the returned data shape. Given no annotations and a single optional parameter, the description should at least hint at the fields or use cases (e.g., APY, TVL). Incomplete for an agent to reliably interpret results.

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% for the single optional parameter vaultAddress, which is already well-described in the input schema. The tool description does not add additional meaning beyond the schema, so 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?

Description states a specific verb ('Get'), resource ('detailed information about Yearn vaults'), and scope ('on Katana network'). It clearly distinguishes from sibling tools like depositToYearnVault, withdrawFromYearnVault, and getUserYearnPositions which focus on user actions or positions rather than vault info.

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?

No guidance on when to use this tool versus alternatives. Does not mention prerequisites, such as needing to know vault addresses, or when it is appropriate to call before deposit or withdrawal operations. The description implies no exclusions but provides no explicit context.

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