vault_status

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

With no annotations, the description carries the full behavioral burden. 'Never secrets' is a genuinely useful guarantee about what the response excludes, but nothing is said about whether this is a read-only operation, what the connection state values look like, whether the 'safe browser link' is always present or only in some states, or whether the call has side effects. This is a significant gap for the only available source of behavioral context.

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?

Seven words is admirably short and front-loaded, but the brevity comes at the cost of a verb and any usable context, so it reads as under-specification rather than effective concision. The semicolon clause about secrets is the strongest part of the sentence and is buried at the end.

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?

This is a low-complexity, zero-parameter tool, which lowers expectations, but there are no annotations and no output schema, so the description is the only place an agent can learn what comes back. It names two return concepts without explaining their shape or relation, and it omits differentiation from the closely related get_connection_status sibling.

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 takes zero parameters and the schema is empty with additionalProperties=false, so there is nothing for the description to clarify. Baseline 4 applies for a no-parameter tool.

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 is a noun phrase with no verb: 'Connection state and safe browser link' essentially restates the name vault_status rather than stating what the tool does (e.g., 'Returns the current vault connection state and a safe browser link'). It also fails to distinguish this from the sibling get_connection_status, whose purpose appears to overlap. Only the 'never secrets' clause adds anything an agent could not infer from the name.

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?

There is no when-to-use guidance at all — no indication of when an agent should call vault_status versus get_connection_status, vault_result, or vault_list. The agent must infer the trigger condition entirely. No exclusions or prerequisites are stated.

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