set_default_workspace

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

The description adds meaningful behavioral context beyond the annotations: it discloses that the operation is a purely local persistence action and never makes a network call to Bitbucket. It also clarifies that the profile is either active or explicitly named. This does not contradict the readOnlyHint=false, destructiveHint=false annotations.

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, focused sentence with the key verb and scope at the front. Every clause earns its place: the active/named profile behavior and the 'purely local' constraint are both valuable and clearly stated.

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 simple two-parameter local mutation, the description covers the behavioral context well, but it leaves the meaning of the workspace parameter and the exact return behavior unstated. Since there is no output schema and no parameter documentation, an agent still has to infer some details about how to supply the workspace value.

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 0%, so the description must compensate, but it does not explain the required 'workspace' parameter at all. It only hints at the optional 'profile' parameter via 'or explicitly named profile.' The schema's 'profile' property is also an unusual $ref, and no meaningful parameter guidance is given.

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 uses a specific verb ('Persists') and clearly names the resource ('a default workspace') and the scope ('on the active (or explicitly named) profile'). It also distinguishes this from siblings like set_active_profile and clear_default_workspace by emphasizing it stores the default workspace locally.

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 clear local-only context: 'Purely local — never calls Bitbucket' tells an agent this is the right tool when no remote interaction is desired. It does not explicitly name alternative tools or list when-not-to-use conditions, but the local/remote contrast is a strong usage signal.

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