manageRewrites

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

No annotations exist, so description carries burden. It details that add creates, list shows existing, delete removes, and dependencies on entry_id from list. This is transparent for a CRUD operation, but lacks info on permissions or rate limits. Score 4.

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?

Description is well-structured, concise, and front-loaded with purpose. Examples are efficient. Score 5.

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 output schema present, description need not explain return values. It covers operations and parameter requirements. It is complete for managing rewrites, given sibling tools context. Score 4.

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 coverage is 0%, but description compensates by explaining the operation enum and required params for each operation with examples. It clarifies that name and content are needed for add, entry_id for delete. Score 4.

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 manages DNS rewrite entries, distinguishes from sibling tools (manageProfiles, etc.) by focusing on rewrites. Provides specific verb and resource (manage rewrites) and explains typical use cases.

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?

While the description explains the operations and examples, it does not explicitly tell when to use this tool over siblings. Implicitly, it's for rewrites, but lacks 'when not to use' guidance. Score 3 because some guidance is provided through examples but not explicit.

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