Switch active LINE OA

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

Annotations indicate idempotentHint=true and no destructive behavior. The description adds transparency by stating 'In-memory only' and specifying return values { active_oa, display_name }, providing behavioral context beyond 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 concise with two sentences and a structured Args/Returns section. Every sentence provides essential information without redundancy, and the main purpose is front-loaded.

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 switching tool with one parameter and no output schema, the description covers all necessary context: purpose, effect duration, persistence behavior, parameter source, and return format. It is complete and self-contained.

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 schema already describes oa_id with 'OA id from line_list_oas'. The description reinforces this by directing to use line_list_oas to discover the oa_id, adding meaningful usage guidance. With 100% schema coverage, the description adds value.

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 uses a specific verb 'Switch' and resource 'active OA', clearly stating the tool's function. It distinguishes itself from siblings like line_list_oas and line_send_message by focusing on switching the default OA context.

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 explains when to use (to switch default OA for subsequent calls) and when it takes effect (until changed or process restarts). It also clarifies what it does not do (does not edit config file) and references line_list_oas for discovery, but lacks explicit alternative usage or when not to use.

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