AxKnowledgeBase_get_knowledge_base_schema

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

With no annotations provided, the description carries the full burden. It indicates a read-only retrieval action ('Retrieve') and describes the returned content, but it does not disclose other behavioral traits such as output format, permissions, or side effects. The description is adequate but not rich.

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 two sentences with no filler. The action is front-loaded, the content is specific, and the secondary sentence adds a clear use case without 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 zero-parameter retrieval tool, the description sufficiently explains what the tool returns (entity types, properties, relationship types, connections) and why it is useful. It does not specify the exact return format, but this is not critical given the tool's simplicity and the absence of an output schema.

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 tool has zero parameters, so the baseline is 4. The description correctly avoids parameter-related information, and the input schema is empty, so there is nothing more to add.

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 verb ('Retrieve') and resource ('knowledge base schema'), and details the contents (entity types with properties, relationship types with properties and connections). It does not explicitly differentiate from sibling tools like get_knowledge_base_overview or knowledge_graph_read, but the purpose is unambiguous.

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 phrase 'Useful for understanding what kinds of information the knowledge base holds' implies a context of use, but it does not specify when to choose this tool over alternatives or mention any exclusions. There is no explicit guidance about 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.