mureo_strategy_get

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

Discloses that absent file returns empty markdown (not error) and that paths outside cwd are refused. No annotations, so description carries full burden, and it adequately covers key behaviors.

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 two sentences, no fluff, highly efficient. Every sentence adds value.

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?

Despite no output schema, description explains return format (raw markdown + exists flag, with empty markdown on absence). The tool is simple, and description covers all necessary context.

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 100%, so baseline 3. Description adds that path is optional with default to STRATEGY.md in cwd and that external paths are refused, providing extra context beyond 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?

Clearly states it reads STRATEGY.md and returns raw markdown with an exists flag. Distinguishes from sibling mureo_strategy_set (write operation) by being a read tool.

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 says to use when host lacks filesystem access, and describes default path and behavior on missing file. Lacks explicit when-not-to-use but implies alternatives.

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