switch_model_profile

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

With no annotations provided, the description carries the full burden. It reveals that persistence is limited to `.multi-agent-mcp/.env` file's `MCP_MODEL_PROFILE_ACTIVE` and does not affect `config.json`, which is non-obvious and helpful for understanding side effects.

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 concisely structured with labeled sections (Args, Returns, Notes). Each sentence provides necessary information without redundancy or superfluous content.

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?

The description covers the essential aspects: purpose, ownership, parameters, return format, and persistence behavior. The presence of an output schema (not provided in context) reduces the need to detail return values. Minor gaps include lack of error handling details and the parameter requirement mismatch.

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 coverage is 0%, so the description must compensate. It lists each parameter with a description, including possible values for profile ('standard/performance'). However, it erroneously marks caller_agent_id as required ('必須'), while the schema shows it is optional with a default of null, which could mislead the agent.

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 the tool's action ('Switch model profile') and specifies that only the Owner can use it. Among siblings like get_model_profile and get_model_profile_settings, this stands out as the mutation counterpart, making its purpose distinct.

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 provides usage context by noting the 'Owner only' restriction and listing required arguments. However, it does not explicitly differentiate when to use this tool versus alternative tools (e.g., get_model_profile to read the current profile).

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