set_session

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

Annotations already convey readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the mutation profile is covered. The description adds meaningful behavioral context: setting names must match what get_session reports, and valid names depend on the Transmission version. This goes beyond the structured annotations.

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 compact and front-loaded with the core action. The parameter explanation is concise, example-driven, and directly useful, with no filler or redundant restatement of the schema.

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 settings-mutation tool with an open-ended object parameter, the description provides the essential discovery mechanism: consult get_session. Output schema and annotations cover return and safety expectations. A minor gap is not stating what happens with invalid or partially specified settings, but the guidance to read get_session first largely mitigates that.

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%, so the description carries the full burden for the settings parameter. It explains that settings is a mapping from get_session-reported names to new values, provides two concrete examples, and instructs the agent to read get_session first. This is exactly the semantic guidance needed for this open-world object 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 begins with a precise verb and resource: 'Change session settings.' It clearly distinguishes this tool from siblings like set_torrent and set_bandwidth_group by targeting the session-level settings object, and the examples reinforce the exact 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?

The description gives clear, actionable usage guidance: read get_session first, use setting names exactly as get_session reports them, and be aware that names differ between Transmission 3 and 4. It does not explicitly discuss alternatives or when not to use this tool, but the session-vs-torrent distinction is clear enough.

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