wisdom_get_fragment

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Retrieve a fragment by UUID,' which adds little beyond the tool name. It does not state what is returned, whether errors occur for missing UUIDs, or whether any side effects exist.

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 short sentence with no filler and the key information is front-loaded. It is appropriately concise for a simple one-parameter retrieval tool, though it is slightly under-specified in terms of behavioral context.

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 trivial single-parameter get operation, the description is minimally adequate for selecting and invoking the tool. However, with no output schema and no annotations, it leaves the return value and the distinction from list/search tools unexplained, which a fuller description could have covered.

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%: the only parameter, uuid, is documented as 'Fragment UUID.' The description repeats this concept without adding format, example, or constraint details, so it provides no meaningful value beyond the schema.

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 verb ('Retrieve') and resource ('fragment') with the access key ('by UUID'). This makes the core function clear and distinguishes it from siblings like wisdom_list_fragments and wisdom_search_fragments, though it does not explicitly name those alternatives.

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 'by UUID' implies the tool should be used when a specific fragment identifier is known. However, there is no explicit guidance about when to prefer this over wisdom_list_fragments or wisdom_search_fragments, and no exclusions or prerequisites are mentioned.

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