get_kb_spaces

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

With no annotations provided, the description carries the full burden. It states the tool lists spaces, but does not disclose details like pagination behavior, ordering, or whether all spaces are listed. The presence of 'maxResults' implies a limit, but this is not explained. The description is minimal but not misleading.

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 extremely concise with two sentences. The first sentence directly states the action, and the second adds context. No superfluous information, and the important points are 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 the simplicity of the tool (two optional parameters, no output schema), the description covers the essential purpose and usage context. It lacks some details (e.g., whether authentication is needed, default behavior for type filter), but overall it is sufficient for an agent to use correctly.

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 coverage is 100%; both parameters already have clear descriptions. The tool description adds no additional meaning beyond what is in the input schema. Thus, it meets the baseline but does not elevate it.

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 ('List') and resource ('available Confluence/KB spaces'), clearly distinguishing it from sibling tools like 'get_kb_page' and 'search_kb_pages'. It also provides context by noting it's useful for discovering space keys before searching.

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 explicitly states the use case: 'Useful for discovering space keys before searching.' This gives clear guidance on when to use the tool. However, it does not mention alternatives or when not to use it, which would strengthen it.

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