get_metadata

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered and the [READ] tag is largely redundant. The only added context is the underlying endpoint path, which hints that this is a system-level read, but nothing is said about auth requirements, caching, or what the metadata contains.

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?

Two short lines with zero filler and the purpose front-loaded; the endpoint line is compact and structured. It is efficient, though arguably so terse that the header-like phrasing borders on under-specification rather than crispness.

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-param read tool with no output schema, the description is minimally sufficient but leaves the key ambiguity unresolved: what 'metadata' actually returns and why it differs from the many other system-info siblings. No return-value detail is expected given no output schema, so this lands at the minimum-viable level.

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, so the baseline of 4 applies. There is no parameter syntax or meaning the description could usefully add.

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?

It states the verb 'Get' and the resource loosely as 'Remnawave Information', plus the concrete endpoint [READ] GET /api/system/metadata. However, 'information' is nearly a restatement of the name 'get_metadata' and does not distinguish this tool from siblings like get_stats, get_status, or get_remnawave_health, all of which also return system-level information.

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?

The description gives no when-to-use guidance and names no alternatives, despite a crowded sibling set (get_stats, get_status, get_remnawave_health, get_configuration) that an agent must choose between. Nothing tells the caller what condition selects this tool.

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