get_kb_instructions

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

No annotations are provided, so the description carries the burden. It explicitly says 'Read', indicating a non-mutating operation, and adds 'with all versions' to clarify the scope. However, it does not disclose potential errors, auth requirements, or return structure beyond what the output schema may cover.

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?

Single sentence, direct, with no filler. It communicates the operation and key detail (all versions) efficiently.

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 tool has one parameter and an output schema. The description covers the core behavior (read all versions). It lacks explicit error handling or alternative guidance, but for a simple read with output schema, it is adequate.

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 has 0% description coverage for knowledge_base_id. The description mentions 'knowledge base' but does not explicitly define knowledge_base_id as the identifier or provide formats/source. The parameter name is self-explanatory, offering partial compensation.

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 'Read' and the resource 'instructions attached to a knowledge base', with the detail 'with all versions'. This distinguishes it from sibling tools like get_kc_instructions (knowledge cluster) and update_kb_instructions (write operation).

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 when to use: to read knowledge base instructions. It does not explicitly mention alternatives or exclusions, but the context is clear from the resource type. No guidance about when not to use (e.g., for clusters), but the intent is obvious.

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