Switch Loaded SAP MCP Profile

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

Annotations include destructiveHint=false and readOnlyHint=false, but the description adds context by mentioning that the tool reloads client, signer, connection, and policy. However, it does not detail the extent of state changes or whether the switch is reversible.

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 sentence that is front-loaded with the main action and includes essential side effects. Every word contributes value, with no unnecessary information.

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?

Given the tool has a simple interface (2 parameters, no required ones, output schema present), the description is largely complete. It could be improved by explicitly stating that the profile must already exist in the runtime, but it is adequate for the given context.

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 description coverage is 100%, so the schema already explains both parameters. The description does not add additional meaning beyond what the schema provides, such as format or examples for 'profileName'.

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 verb 'Switch' and the resource 'SAP MCP profile', and it distinguishes this from sibling tools like 'sap_profile_list' (list profiles) and 'sap_profile_current' (show current) by specifying that it switches the runtime and reloads components.

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 notes that `confirm` must be true because the switch changes signer, network, and policy, which provides a usage constraint. However, it does not explicitly state when to use this tool vs alternatives, such as when only viewing the current profile is needed.

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