list_sync_rules

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

The annotation readOnlyHint=true already declares this as a read-only operation, and the description adds the behavioral detail that it lists all rules without filtering. It doesn't disclose pagination or ordering, but with the annotation covering safety, the description provides adequate context.

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 two sentences, immediately starting with the action and resource. It efficiently clarifies what a sync rule is and what data is returned, leaving no redundant text.

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?

With no parameters, an output schema, and a read-only annotation, the description covers the essential information: the action, the resource, and the returned fields. It could mention potential limitations like pagination, but for a likely simple listing tool, this is adequate.

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 tool has zero parameters, so the baseline is 4. The description correctly states it lists all rules and enumerates the return fields, which is sufficient given the absence of parameter requirements.

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 uses the specific verb 'List' with the resource 'sync (mirror) rules' and explains the rule's function. It clearly distinguishes from sibling tools like create_sync_rule and delete_sync_rule by focusing on listing. The returned fields are enumerated.

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 implies this tool is for viewing existing sync rules, but it doesn't explicitly state when to use it versus alternatives like run_sync_rule or delete_sync_rule. However, the context of sibling names and the 'list all' phrasing provides clear context for the listing use case.

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