Reset the company skill policy to the open default

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

Annotations already provide destructiveHint=true and other flags. The description adds the HTTP DELETE method and authorization class, but does not disclose side effects or additional behavioral context beyond what annotations convey.

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 extremely concise: two sentences stating the purpose and operation details. No extraneous information, every sentence adds value.

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 simple reset operation, the description provides purpose, HTTP method, and authorization class. An output schema exists, so return values need not be described. However, it lacks explanation of 'open default' and any prerequisites.

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?

With schema description coverage at 50%, the description adds no parameter details beyond the schema. The path.companyId parameter lacks any description, and the description does not clarify its purpose or format.

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 title and description clearly state 'Reset the company skill policy to the open default', specifying a clear verb (reset) and resource (company skill policy). This distinguishes it from sibling tools like GET (retrieve) and PUT (update).

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 usage for resetting to the open default, but does not explicitly state when to use this tool versus alternatives like GET, PUT, or POST evaluate. No exclusions or alternate scenarios are mentioned.

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