mureo_state_get

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

Describes read operation and edge case (empty default doc when file absent). No annotations provided, so description carries the burden; it could explicitly state no side effects, but 'Read' strongly suggests read-only behavior.

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 sentences, front-loaded with core functionality and fields, then edge case. No redundant information. Every sentence earns its place.

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?

No output schema, but description sufficiently explains return content and default behavior. Could briefly mention the format of 'v2 document', but listed fields provide adequate understanding.

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 covers parameter description (100% coverage). Description adds value beyond schema by clarifying default path and restriction (paths outside cwd refused), aiding correct invocation.

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?

Description clearly states the tool reads STATE.json and returns a parsed v2 document, listing all fields (version, last_synced_at, platforms, legacy campaigns, action_log). The verb 'Read' and specific resource distinguish it from sibling tools like mureo_state_upsert_campaign.

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?

Implies usage for reading state, but no explicit guidance on when to use vs alternatives (e.g., mureo_strategy_get) or when not to use. No exclusions or prerequisite conditions mentioned.

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