mureo_strategy_get

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses key behaviors: returns empty markdown for absent files (not an error), includes server_now for clock accuracy, and explains the impact of notices (workspace-bound skills stop). It also mentions path restrictions (paths outside cwd refused). However, it doesn't elaborate on error handling for other failures or the exact format of the empty response, but the main behaviors are transparently communicated.

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 well-structured, with the primary purpose stated first, followed by critical usage notes. It's concise, with every sentence providing value: the return fields, the notice explanation, the empty behavior, the host accessibility cue, and the time guidance. Front-loading the core function and interleaving essential context makes it efficient and readable.

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?

For a simple read tool with one optional parameter and no output schema, the description is quite complete. It covers return fields, edge cases (file absent), environmental signals (notices), and usage restrictions (cwd). The only gaps are potential details on error codes or logging, but these are not critical for correct invocation. Given the tool's simplicity, this is near-complete.

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 schema description covers 100% of the parameter (path) with a description that includes defaults and restrictions. The tool description adds minimal extra meaning beyond that: it mentions the path is optional and that it defaults to STRATEGY.md/STATE.json, which is already in the schema. Since schema coverage is high, baseline is 3, and the description doesn't significantly enhance parameter understanding, so a 3 is appropriate.

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 purpose: reading STRATEGY.md and returning its raw markdown along with metadata. It specifies the resource (STRATEGY.md), the verb (read), and the return fields (markdown, exists flag, path, server_now, workspace_id, notices). Among the mureo_* siblings, it's distinct from mureo_strategy_set and mureo_state_get, and the description differentiates it by focusing on the strategy file read. The clarity is high and specific.

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 states when to use this tool: when the host has no direct filesystem access (e.g., Claude Desktop chat, web, remote MCP). It also provides critical usage guidance: treat server_now as the current date and never infer today from context files. It doesn't mention when not to use it in favor of alternatives, but the context signal is strong enough. While alternatives like mureo_state_get might exist, the description's use case is clear and leaves no ambiguity about when to invoke it.

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