mureo_strategy_get

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

Discloses that missing file returns empty markdown (non-error), and mentions that paths outside cwd are refused. Without annotations, the description fully covers behavioral traits.

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?

Two concise sentences, front-loaded with key action and return info. Every sentence earns its place with no wasted words.

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?

With no output schema, the description explains the return format (raw markdown + exists flag) and handles the edge case of absent file. Complete for a simple read tool.

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% with a good description of the path parameter. The tool description adds value by clarifying the use case (no direct filesystem access) but does not add extra meaning beyond the schema. Minor mismatch: tool description only mentions STRATEGY.md while schema mentions STATE.json as well, but this is not a major issue.

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 plus an exists flag. Distinguishes itself from the many Google Ads and Meta tools, as it is the only tool for reading strategy files.

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 the host has no direct filesystem access, listing contexts like Claude Desktop chat, web, and remote MCP. Also clarifies that absent file should be treated as 'no strategy yet', not an error.

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