Set Active Tenant

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

With no annotations, the description discloses persistence across sessions, clearing behavior, and effects on query/execute. Does not mention error handling for invalid tenantUrl, but the requirement to match status tool output is noted.

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?

Two sentences with no waste; all information is relevant and 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?

Given one parameter and no output schema, the description covers all needed context: setting, clearing, persistence, and effects on sibling tools. No gaps for a CLI session tool.

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 0% schema description coverage reported, the description clarifies the parameter's role (pass null to clear, must match status tool output), adding meaning beyond the schema's own description. Compensates for coverage gap.

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?

Description clearly states the tool sets the Cumulocity tenant for the CLI session, with specific verb 'Set' and resource 'tenant'. It distinguishes from sibling tools by explaining how tenants are selected from the status tool output and how clearing affects execute/query.

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?

Provides clear guidance on when to use (once per session or when switching tenants) and what happens when clearing (query works but execute unavailable). Lacks explicit contrast with sibling tools but context is sufficient.

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