Tribal: Get Knowledge Item by ID

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

With no annotations, the description carries full transparency burden. It reveals response behavior (keyed by ID, missing IDs map to null) and implies read-only usage via 'retrieve.' However, it does not explicitly state side-effect freedom or authorization needs, though the retrieval nature is clear.

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 front-loads the core action, then provides focused usage guidance and response details in just three sentences. Every sentence is necessary and adds value, with no redundancy or filler.

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 tool has 3 parameters, an output schema, and sibling tools, the description completes the picture by specifying when to use, limitations (direct lookup), and response format. It does not need to explain return values (output schema exists) and covers all essential contextual aspects.

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 100%, so baseline is 3. The description does not add extra meaning to parameters beyond what the schema provides (e.g., include_references, include_standing are described in schema). Thus, it meets the baseline without surpassing 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 starts with 'Retrieve one or more knowledge items by their IDs,' clearly stating the verb and resource. It explicitly distinguishes this tool from siblings (tribal_discover for semantic search, tribal_explore for relationship traversal), making its specific purpose unmistakable.

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 provides explicit usage context: 'Use this when you have a specific item ID ... and need the full item.' It also clearly states when not to use it, directing to alternative tools for semantic search and relationship traversal, leaving no ambiguity about selection.

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