hosting_listNode_jsEnvironmentVariablesV1

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

With no annotations present, the description carries the full burden and handles it well: it discloses that values are always masked as `********`, that they cannot be read back through this API, and that the companion replace operation overwrites the whole set. The read-only, non-leaking nature of the call is clear. Minor gaps remain—permission requirements and behavior on non-Node.js sites are not mentioned—but the most safety-critical traits are disclosed.

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?

Approximately two short paragraphs, front-loaded with the purpose, followed by the critical behavioral caveat and the usage warning. Every sentence earns its place—there is no filler, and the anti-pattern warning (never copy masked values into the replace call) is high-value safety information.

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 tool with only 2 simple parameters and no output schema or annotations, the description is nearly complete: purpose, response behavior (masked keys), correct usage, and the dangerous interaction with the sibling replace endpoint are all covered. The only gaps are minor edge conditions like error behavior or handling of non-Node.js websites, which are not critical for correct invocation.

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 coverage is 100%, so the baseline of 3 applies. The description adds no parameter-level meaning beyond the schema, and the schema's own descriptions are thin ('username parameter' is essentially a tautology). This is not a deficiency in the description, but it does not compensate for the weak schema wording, so the score stays at the baseline.

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?

States a specific verb ('Lists') and a specific resource (Node.js environment variables for a website), and immediately clarifies the scope: it shows which keys are configured, not their values. The masking caveat distinguishes this from any naive expectation that env vars can be read back, and the explicit contrast with the sibling 'Replace Node.js environment variables' endpoint separates it from the write operation.

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?

Gives explicit when-to-use guidance ('see which keys are configured or to verify a change') and an explicit exlusion ('not to read values'). It names the alternative endpoint directly and warns against the specific misuse of copying masked values into the replace request. This is model guidance for routing an agent to the correct tool.

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