set_network

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

Annotations already indicate readOnlyHint=false (mutator), destructiveHint=false (safe), and idempotentHint=true (repeatable). The description adds behavioral context by stating the scope ('global default') and the override behavior, but doesn't elaborate on side effects or persistence.

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, clear sentence of 14 words. It is appropriately concise and front-loaded, though it could benefit from a brief structure (e.g., listing valid networks) without being verbose.

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 simple setter tool with one parameter and annotations present, the description covers the essential purpose and effect. However, it omits details like what happens if an invalid network is provided, whether authentication is required, and if the setting persists across sessions. These gaps reduce completeness.

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 input schema provides full description for the single 'network' parameter, listing valid options (mainnet, nile). The description adds context about the parameter's effect on subsequent operations but does not add new semantic information beyond the schema.

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 that the tool sets a global default network for JustLend operations. It distinguishes itself from sibling tools like get_network (which reads the current network) and get_supported_networks (which lists options). However, it does not explicitly contrast with these alternatives.

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 usage when you want to set a default network that applies to all subsequent operations unless overridden per operation. But it does not specify when to use this versus passing the network directly in each operation, nor does it mention prerequisites or when not to use it.

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