campus_close

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

Annotations say not read-only, not destructive, not idempotent, open-world. The description adds what the annotations cannot: it waits for in-flight downloads and preserves the profile locally, so state survives the close. It is silent on whether anything in the browser session is lost.

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?

Two short sentences, front-loaded with the action and its timing constraint. Every clause (the downloads wait, the profile retention) conveys information an agent could act on.

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 single-enum-parameter lifecycle tool with annotations and no output schema, this covers the timing, the target, and the persistence outcome. What remains unsaid is whether a stuck download blocks the close and what result is returned, which a 4 tolerates.

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?

One required parameter with 0% schema description coverage, but it is a closed enum (csmar, cnrds) carried by the input schema. The description scopes the action to 'a provider browser', which ties the enum to the subject being closed; little else is needed.

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 (close) and resource (a provider browser), names the lifecycle sibling campus_open, and adds the distinguishing condition 'after active downloads finish' plus the profile-retention behavior. An agent can tell it apart from campus_downloads and campus_open immediately.

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 phrase 'after active downloads finish' is an explicit prerequisite and timing condition, so an agent knows not to call it prematurely. It stops short of naming alternatives or saying when not to close, which keeps it at 4.

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