get_bundle

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

With no annotations, the description carries the behavioral burden and does disclose the key behavior: it concatenates all module Markdown and appends an overlay if present. It also signals a read operation via 'Pobierz'. It does not discuss failure modes or permissions, but for a simple fetch tool that is a minor gap.

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 compact, front-loads the core purpose, and uses a clear Args/Returns structure. Every sentence adds information with no 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?

For a single-required-parameter read tool with an output schema, the description covers purpose, parameter meaning, and return format. It omits exact allowed bundle names and error behavior, but these are not critical for a straightforward fetch by name.

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 coverage is 0% and the schema only labels the property 'Name', so the description compensates by defining name as the bundle identifier and giving concrete examples ('backend', 'frontend', 'architecture', 'full'). It could be stronger with an exhaustive enum or validation rules, but the compensation is sufficient for correct invocation.

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 uses a specific verb ('Pobierz' – fetch) and a precise resource ('pełną treść bundle'a instrukcji'), and clarifies that the result is the combined Markdown of all modules plus optional overlay. This distinguishes it from siblings like get_module (single module) and list_bundles (listing bundles).

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 this tool is for retrieving the full assembled content of a bundle and gives name examples, but it does not explicitly state when to prefer it over get_module or get_overlay, nor does it mention exclusions. Usage context is left largely to inference.

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