Set Active Tenant

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It clearly states persistence across sessions, the effect of clearing, fallback to bundled-only browsing, and unavailability of live API calls until a tenant is set again. This is excellent transparency for such a simple state-setting tool.

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 three sentences with every sentence earning its place: core action, persistence/constraint, and fallback behavior. It is front-loaded and contains no filler or redundancy.

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 one-parameter tool with no output schema and no annotations, the description is complete. It covers setting, clearing, valid input source, persistence, and downstream behavior, giving the agent enough context to select and use the tool correctly without additional lookups.

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?

Despite the reported 0% schema description coverage, the tool description fully compensates by explaining that tenantUrl must match a value from the status tool and that null clears the active tenant. With only one parameter, this gives the agent everything needed to invoke the tool correctly.

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 sets or clears the active Cumulocity tenant, with explicit mention of the null value to clear. It uses a specific verb and resource, and distinguishes itself from status and codemode by connecting tenantUrl to status output and explaining fallback behavior.

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 explicit usage guidance: call once at session start or when switching tenants, pass null to clear, and understand that codemode discovery remains available but live API calls do not. It also tells the agent that the value must come from the status tool, providing clear context for when to use this tool vs alternatives.

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