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

With no annotations, the description carries the full behavioral burden and does disclose key traits: server-side substitution, sending the request, returning status/scrubbed body, and never returning the secret. It omits important context such as permissions, error behavior, and side effects of the outbound request.

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 short, front-loaded, and free of filler. Each sentence adds operational information about substitution, sending, and return 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?

The description covers the central mechanism and return safety, but for a tool with five undocumented parameters, no annotations, and no output schema, it leaves gaps around method defaulting, body semantics, purpose meaning, and request error behavior.

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?

Schema description coverage is 0%, so the description must compensate, but it only partially explains name usage via [vault:name] and notes that purpose is required. It does not explain method, body versus url handling, or what purpose semantically represents.

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 explains that this tool substitutes a vault secret into an HTTP request and sends it, returning status and a scrubbed body. It is specific about the core mechanism and return behavior, though the verb 'Use' is less precise than a dedicated operation 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?

The description implies when to use it by telling the caller to put [vault:name] in url or body when a secret must not be exposed. However, it does not explicitly compare against alternatives or state when not to use it.

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