Set map variable

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

The description only states 'Write', indicating mutation, but provides no details on permissions, side effects, or behavior when the variable already exists. With no annotations, the description carries the full burden and fails to disclose key behavioral traits.

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 a single short sentence with no extraneous text, but it is under-specified and fails to provide sufficient information, thus not earning its place.

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?

Given the complexity of three parameters and no output schema, the description is incomplete. It mentions map-scope but omits details about return values, error handling, and interaction with sibling tools.

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 0%, yet the description only adds 'by name' for the name parameter, leaving value and instance unexplained. It does not meaningfully compensate for the missing schema descriptions.

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 verb 'Write' and the resource 'a map-scope ACS variable by name', effectively distinguishing it from sibling tools like set_acs_var which may imply global scope. However, it does not explicitly compare to siblings, slightly reducing clarity.

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?

No guidance is provided on when to use this tool versus alternatives such as set_acs_var or get_map_var. The description implies it's for map-scope variables, but lacks explicit when-to-use or when-not-to-use criteria.

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