mureo_strategy_set

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

No annotations are provided, so the description bears full responsibility. It discloses atomic replacement, parsing via parse_strategy() for well-formedness, and that malformed input raises an error rather than corrupting the file. It also explains path defaults and restrictions (paths outside cwd refused). This is comprehensive behavioral 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?

Three sentences, no wasted words. The first sentence states the core action, the second adds validation behavior, and the third gives use-case guidance. Efficient and front-loaded.

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 having no annotations and no output schema, the description covers purpose, parameters, validation, atomicity, file location constraints, and intended use context. It leaves no obvious gaps for an agent to decide or invoke the tool correctly.

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?

Input schema has 100% descriptive coverage for both parameters (markdown and path). The description adds value by explaining that the content is parsed and validated before writing, and that the path default is relative to cwd with restrictions. This goes beyond the schema's descriptions.

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 atomically replaces STRATEGY.md with provided markdown. The verb 'replace' and resource 'STRATEGY.md' are specific. It distinguishes from siblings like mureo_strategy_get (read) and mureo_state tools, and from many Google/Meta ad tools.

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 explicitly says 'Use this to update goals, constraints, or operation mode from a chat-only host.' This gives clear context. While it doesn't explicitly state when not to use, the sibling mureo_strategy_get provides an alternative for reading. The chat-only host qualifier adds specificity.

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