post_w_company_reset_agents

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only explains where to place request components. It does not disclose whether the operation is destructive, reversible, idempotent, or what impact it has on agents or company data; 'Migrate Agents Calls' is too vague to count as behavior disclosure.

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 short, but some words are redundant ('request headers in headers', 'request payload in body') and the opening phrase is awkward rather than informative. It is compact enough, but it does not front-load a clear behavioral purpose before the placement instructions.

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?

The description is incomplete for a tool with no annotations and a 0%-coverage schema. It does not explain the operation's purpose, side effects, when to call it, or what the response/output represents, despite an output schema being present. The agent can guess where to put parameters but cannot understand the tool's actual business effect.

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 schema has 0% description coverage, so the description must compensate, and it partially does by mapping path_params to route IDs, query to filters/pagination, headers to required headers, and body to the payload. However, this is still shallow and generic: it gives no concrete key names, value formats, requiredness, or body structure, so the added meaning is minimal beyond the schema's generic object types.

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 opens with the vague phrase 'Migrate Agents Calls' and then repeats the endpoint path, which largely restates the tool name 'reset_agents' as a URL. It does not clearly explain what 'resetting agents' or 'migrating agent calls' actually does, and it offers no meaningful distinction from the many other company-related POST tools.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The only hint is the implicit suggestion that this is for migrating agent calls, but the description never states the conditions under which an agent should select this endpoint instead of a sibling.

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