sassy_env_list

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explicitly states an important behavior: sensitive values (tokens, keys, secrets) are masked. This goes beyond a basic 'list' and helps the agent anticipate security masking. It does not mention permissions or pagination, but these are less critical for a simple list tool.

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 two sentences, front-loaded with the primary action in the first sentence. Every word earns its place—it states the operation, the optional filter, and the sensitive-value masking without redundancy. This is a model of conciseness.

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 simple list tool with one optional parameter and an output schema present, the description is complete. It covers what the tool does, how filtering works, and a critical security behavior. There are no missing pieces that would prevent correct invocation or understanding of results.

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 schema provides no description for the single parameter filter_str (0% coverage), so the description must compensate. It does so by explaining that the filter is optional and matches by name substring, adding meaningful semantics beyond the parameter name and default value. This is sufficient for the sole parameter.

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 states the tool's function with a specific verb and resource: 'List environment variables.' It also distinguishes itself from sibling tools like sassy_env_get and sassy_env_set by focusing on listing rather than retrieving or setting a single variable. The optional substring filter further clarifies intent.

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 provides clear context for when to use the tool: whenever you need to list environment variables, optionally filtered by name substring. It does not explicitly mention alternatives or exclusions (e.g., 'use env_get for a single variable'), but the scope is self-evident and consistent with the tool's name and siblings.

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