mureo_learning_insights_get

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

No annotations provided, but description fully discloses read-only behavior, output format (raw Markdown), and the fallback guidance string when no insights exist. No contradictions.

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?

Description is concise, front-loaded with purpose, and logically structured. Every sentence adds value without redundancy.

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?

Completely describes input (none), output (raw Markdown or guidance string), behavior (read-only), and timing (start of diagnostic workflows). No gaps given no output schema.

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?

No parameters exist; input schema has 100% coverage trivially. Description adds no parameter detail needed, but baseline is 3. The tool's simplicity earns a 4 for clarity.

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?

Clearly states it loads insights saved via /learn, returns raw Markdown, and is read-only. Distinguishes from sibling tools like mureo_state_get or mureo_consult_advisor by focusing on practitioner know-how.

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?

Explicitly instructs to call near the start of diagnostic workflows before drawing conclusions. Lists specific workflows (/daily-check, /rescue, etc.) and explains why (so insights inform analysis).

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