mureo_learning_insights_get

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

With no annotations provided, the description carries the full transparency burden. It discloses that the tool is read-only, describes the return format ('raw Markdown in one payload'), explains the tier structure and precedence rules, and notes the edge case of no insights. This is thorough and goes well beyond minimal disclosure.

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 appropriately sized for the tool's complexity. It front-loads the core purpose, then adds necessary detail about tiers, precedence, and usage timing. Every sentence earns its place, including the list of workflow names, which serves as practical guidance rather than 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?

Without an output schema, the description fully compensates by detailing return values (tiers, labels, precedence, empty-case guidance string) and usage context. It is complete for a simple getter tool with no parameters and no destructive actions.

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 tool has zero parameters, so the baseline is 4. The description correctly avoids parameter explanations since none exist, and the schema fully covers the (empty) parameter space.

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 tool's function: 'Load every insight previously saved via /learn.' It specifies the exact resource (insights saved via /learn) and the action (load), and distinguishes it from sibling tools by describing the two-tier structure (operator and workspace), which no other tool mentions.

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 gives explicit usage timing: 'Call this near the start of every diagnostic workflow... BEFORE drawing conclusions.' It lists specific workflows and provides rationale. However, it does not explicitly mention when not to use it or alternatives (though none exist among siblings), so it falls short of a 5.

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