get_vault_status

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

No annotations are provided, and the description does not disclose any behavioral traits such as read-only nature, authentication requirements, or side effects. The word 'Complete' is ambiguous regarding what is returned. The description adds minimal transparency beyond the tool name.

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 extremely concise (3 words) and front-loaded with the key information. However, the term 'Complete' could be clarified. It earns its place but could be slightly more informative without much overhead.

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 lack of output schema and annotations, the description leaves out what 'vault position status' includes. For a tool with no parameters, users still need to understand the format or scope of the returned data. The description is insufficient to fully understand the tool's output or behavior in the context of sibling vault 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?

The tool has no parameters, and the schema coverage is 100% (trivially). The description provides no parameter information, which is acceptable since no parameters exist. Baseline score of 3 applies because the schema already fully covers the (non-existent) parameters.

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 'Complete vault position status' clearly indicates the tool retrieves a full snapshot of vault position data. The verb 'get' is implied by the name, and the resource is specified. Among many vault siblings, it is distinct from other specific vault queries like get_total_vault_assets, though no explicit differentiation is provided.

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 given on when to use this tool versus alternatives like get_total_vault_assets or get_vault_events. The description does not state context, prerequisites, or exclusions for usage.

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