bitbucket_workspace_list

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

Annotations already declare readOnlyHint and idempotentHint, covering safety. The description adds the 'authenticated account' scope and the concept of a 'configured default', which are useful behavioral details beyond annotations. No contradictions and no need to restate read-only nature.

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: the first states the main action, the second gives usage guidance. Front-loaded, concise, and every sentence earns its place with no 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 simple list tool with one optional param and no output schema, the description covers purpose, usage timing, and the default workspace nuance. Nothing an agent needs to invoke it correctly is missing.

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% for the single parameter maxItems, and the description doesn't mention it at all. The parameter is optional with default/min/max in the schema, so the schema itself is clear, but the description fails to compensate for the low coverage as required. It adds no meaning beyond the schema.

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?

States 'List every Bitbucket workspace the authenticated account can access' with a specific verb (list) and resource (workspaces). It also distinguishes itself from siblings by explaining its role in discovering slugs before other tools and finding non-default workspaces, making it clear which tool to pick.

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 explicit context: 'Use this to discover a workspace slug before calling any other tool, or to find one other than the configured default.' This tells the agent when to invoke it, though it doesn't explicitly mention when not to use it or name alternatives. Clear context without exclusions.

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