memory_sync_rules

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

No annotations are provided, so the description must carry the full burden. It mentions returning 'structured JSON for cross-session persistence' but does not disclose side effects, permissions, error handling, or behavior when no active rules exist.

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 concise with two sentences and an 'Args' section. It is front-loaded and efficiently communicates the tool's purpose and primary parameter, though the 'Args' format is somewhat minimal.

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?

Given that an output schema exists (context: 'Has output schema: true'), the description need not detail return values. However, it lacks information about prerequisites, error scenarios, or how 'active prevention rules' are determined, leaving some gaps for a simple data generation 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?

The description explains 'limit' as 'Max number of rules to sync', which adds meaning beyond the schema's type and default. Since schema description coverage is 0%, this description effectively compensates for that gap.

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 states a specific verb ('Generate') and resource ('mcp-server-memory payloads for active prevention rules'), clearly distinguishing it from siblings like 'memory_sync_decisions' or 'memory_sync_mistakes' which sync different data types.

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?

No guidance on when to use this tool versus its siblings or alternatives. The description only states what the tool does without providing context about when it's appropriate or when not to use it.

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