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

With no annotations, the description carries the full burden. It adds value by noting the terms are 'live' and listing the covered fields, but it does not disclose potential behaviors like data freshness guarantees, error cases, or whether the data is sourced on-chain or via API. For a simple zero-parameter getter, this is acceptable 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?

The description is a single, front-loaded sentence that lists all key terms without waste. Every piece of information ('live', vault name, field list) contributes to understanding what the tool returns.

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 zero-parameter tool with no output schema, this description covers the return content well by listing all major deposit term categories. It is not exhaustive about formatting or potential edge cases, but it is sufficiently complete for a simple getter.

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 is empty, so there are no parameter semantics to explain. The baseline of 4 applies because the description correctly implies no inputs are needed and focuses on the returned content.

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 identifies the resource (live SukukFi vault) and enumerates specific contents (target yield, capacity, minimum ticket, lockup, accepted assets, settlement cycle), distinguishing it from sibling tools like get_vault_stats. It lacks an explicit verb, but the tool name and context make it an obvious retrieval operation.

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 is provided on when to use this tool versus alternatives such as get_vault_stats or get_contracts. The intended use is implied by the resource name and field list, but no explicit context or exclusions are given.

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