Get Knowledge Base

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

The description adds minimal behavioral context beyond what annotations already provide. Annotations indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe nature is already clear. The description mentions 'detailed information' but does not specify what details are returned or any potential performance implications.

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 sentence that is direct and to the point, containing no unnecessary words or fluff.

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 (single parameter, no output schema, good annotations), the description is nearly complete. It could be slightly improved by hinting at what 'detailed information' includes, but overall it provides sufficient context for the agent to understand the tool's functionality.

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 schema already describes the 'id' parameter as 'Unique identifier of the knowledge base' with 100% coverage. The description does not add additional meaning, so the baseline score of 3 is appropriate.

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 specific action ('Retrieve'), the resource ('detailed information about a specific knowledge base'), and the input ('by its ID'). This distinguishes it from list_knowledge_bases and other related tools.

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 usage for retrieving a single knowledge base by ID but does not explicitly state when to use it versus alternatives like list_knowledge_bases or search_knowledge. The context from sibling tools provides some guidance, but the description itself offers no explicit when-to-use or when-not-to-use information.

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