Rules Sync

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

With no annotations provided, the description carries the full burden. It describes key behaviors: scanning for specific agent rule files, deduplication, conflict detection, and conditional output generation. However, it doesn't disclose important operational details like whether files are modified in place, where generated files are saved, error handling, or performance characteristics.

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 efficiently structured in two sentences that front-load the core functionality and then explain the conditional behavior based on parameters. Every word earns its place, with no redundancy or unnecessary elaboration.

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 tool with 2 parameters, 100% schema coverage, but no annotations and no output schema, the description provides adequate context for basic usage. However, it lacks details about output format, file system interactions, error conditions, and specific behavioral constraints that would be needed for complete 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 description coverage is 100%, so the baseline is 3. The description adds value by explaining the semantic relationship between parameters: 'Without target: returns sync status report. With target: generates converted rule files.' This clarifies how the 'action' and 'target' parameters interact, which goes beyond the schema's individual parameter 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's purpose with specific verbs ('scan', 'deduplicate', 'detect conflicts', 'generate') and resources ('agent rule files', 'target agent format'). It distinguishes from siblings by focusing on rule file synchronization rather than other memorix operations like consolidation, search, or workspace management.

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 the tool: 'Without target: returns sync status report. With target: generates converted rule files.' This provides clear guidance on the two usage modes based on whether the target parameter is provided, distinguishing between status checking and file generation.

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