sassy_env_get

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 accurately states the key error condition ('Returns error if not set'), which is valuable. The word 'Get' implicitly indicates a read operation with no side effects, though it does not elaborate on permissions or return format.

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 extremely concise, consisting of two short sentences that immediately convey the purpose and a key behavioral detail. No redundant information is included.

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?

This is a simple single-parameter tool. The description covers the core action and the notable error condition, making it sufficient for an agent to understand what to expect. The presence of an output schema likely covers return value details, so the description need not list everything.

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 has one parameter 'name' with no description, and the description does not explicitly map it to the environment variable name. However, 'environment variable value' strongly implies the parameter is the variable name. The description adds minimal meaning beyond the schema, but enough to understand the parameter's role.

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 action ('Get') and the resource ('environment variable value'), making the tool's purpose unambiguous. It is distinct from sibling tools like sassy_env_set and sassy_env_list, which handle different operations.

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 the tool is for reading a specific environment variable, but it does not explicitly state when to use it over alternatives like sassy_env_list or provide any exclusions. The usage context is clear from the name but lacks explicit guidance.

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