protect_restrict

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

No annotations provided; description carries full burden. It does not disclose essential behaviors such as what happens when password is set, whether ranges can be modified later, or if authentication is required. The single phrase is insufficient.

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 (one brief phrase) and front-loaded, but it sacrifices critical detail. It earns its place as a title but fails to provide adequate tool guidance.

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 the tool has 3 parameters, no output schema, no annotations, and numerous sibling tools, the description is severely incomplete. It fails to explain parameter usage, behavioral nuances, or return values.

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 0% and the description adds no meaning to any of the 3 parameters (doc_id, password, ranges). The purpose of 'password' and 'ranges' is unexplained, leaving the agent without guidance on how to use them.

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 name 'protect_restrict' and description 'Restrict editing ranges in the document' clearly specify the action (restrict) and resource (editing ranges). It distinguishes from sibling tools like 'protect_document' (likely protects entire document) and 'unprotect_document'.

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 alternatives like 'protect_document' or 'unprotect_document'. The description does not mention context, prerequisites, or exclusions.

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