gateway_knowledge_space_get

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

The readOnlyHint annotation already signals a safe read operation, and the description's 'Get' wording aligns with that. The description adds little beyond the annotation, such as how the optional 'space' parameter behaves when empty or how missing spaces are handled.

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?

One clean sentence that front-loads the verb and resource and lists the key return categories. No filler or redundant restatement of the tool name.

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?

The presence of an output schema and the read-only annotation reduces the need to describe return values or safety. However, the ambiguous optional 'space' parameter and lack of sibling differentiation leave an agent unsure exactly what value to pass and when this tool is preferable.

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 only parameter, 'space', has no schema description and the description does not clarify accepted formats, default behavior, or whether it expects an ID or name. The only semantic cue is the phrase 'knowledge space', which is thin given 0% schema coverage.

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 states a specific action ('Get') and resource ('knowledge space'), and lists concrete output facets: metadata, members, and document count. It is clear, though it does not explicitly distinguish itself from sibling tools like gateway_knowledge_space_list.

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 the intended use case—retrieving details about a single knowledge space—but provides no explicit guidance on when to choose this tool over related siblings. No alternatives or exclusions are mentioned.

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