api_set_env

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

No annotations are present, so the description carries the burden of exposing side effects. It discloses persistence across subsequent calls and the key merge behavior: 'Merges with existing env unless replace=true.' It could more explicitly state that replace=true discards prior values, but the core behavioral trait is transparent.

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?

Three short, purposeful sentences: what the tool does, how the environment is merged/replaced, and when to use it. The example is useful and there is no filler.

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 configuration tool with no required parameters, no output schema, and no annotations, the description covers the essential invocation context: target fields, persistence, merge behavior, and a typical use case. It could be slightly more explicit about replace=true's exact impact and return behavior, but it is sufficiently complete for correct use.

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?

With 0% schema description coverage and all three parameters undocumented in the schema, the description compensates by explaining baseUrl, defaultHeaders, and especially the replace flag ('Merges with existing env unless replace=true'). It lacks a concrete example for defaultHeaders, but the main parameter meanings are conveyed.

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 opens with a specific verb and resource: 'Set base URL and/or default headers used by all subsequent api_request / api_assert / api_test_suite calls.' This clearly separates configuration from the request/assert/suite sibling tools and defines the tool's scope.

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?

It gives clear context for use ('set baseUrl once at the start of a session') and names the downstream tools it affects. It does not explicitly describe when-not-to-use or name a competing config sibling, but no clear alternative exists among the siblings.

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