vpn_status

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

There are no annotations, so the description carries the full burden of behavioral disclosure. However, 'VPN status.' reveals nothing about side effects, return format, authentication requirements, or what constitutes a status. This is a complete absence of behavioral transparency.

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 only two words, which is extreme under-specification rather than effective conciseness. It lacks a sentence structure and provides minimal value. It is not appropriately sized for a tool that needs to convey its behavior.

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 annotations and output schema, the description should explain what status the tool provides and what the output looks like. It does not, leaving the agent completely uninformed about expected behavior or result format. This is comparable to the 'Process' example in inadequacy.

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 has zero parameters, and schema description coverage is 100% (trivially). With no parameters, there is nothing for the description to add. The baseline for 0 params is 4, and the description does not detract from this.

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 'VPN status.' is a noun phrase that names the resource but lacks a verb. It does not explicitly state what the tool does (e.g., 'Get VPN status'), and it does not differentiate from sibling tools like vpn_connect or vpn_disconnect. This is only slightly more informative than a tautology.

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 usage guidance is provided. The description does not mention when to use this tool, whether it is read-only, or how it relates to other VPN tools or status tools. The agent must infer usage from the name alone.

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