set_subscription

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

The description discloses that it changes the session's active subscription, which is a key behavioral trait. However, it does not mention idempotency, error handling (e.g., invalid subscription_id), or whether the setting persists across calls. Given no annotations, the description provides basic but adequate transparency.

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 (two sentences) and front-loaded with the purpose. While it is brief, it covers the necessary information without superfluous text. Minor improvement could be integrating the parameter format more seamlessly.

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's simplicity (one parameter, no nested objects), the description covers the core action and parameter format. The existence of an output schema reduces the need to describe return values. It is fairly complete for a configuration setter.

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 parameter subscription_id is described with a format hint (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx), which adds meaning beyond the schema's plain string type. Since schema coverage is 0%, this description compensates well by clarifying the expected format.

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 the Azure subscription for the session, using a specific verb ('Set') and resource ('Azure subscription' for session). This distinguishes it from sibling tools that list subscriptions or manage other resources.

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 implies the tool should be used before subscription-specific operations, but does not explicitly state when to use it vs alternatives (e.g., list_subscriptions to find subscriptions first). No guidance on prerequisites or when not to use it.

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