Reorder Company Role

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds that it creates a new Company Settings and returns HTTP 201, but does not disclose permissions, side effects, or rate limits. The openWorldHint=true annotation is not explained.

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 relatively concise (three sentences plus API info) but slightly redundant with 'Reorder Company Role' then 'Use this to perform...'. The API endpoint detail may not be essential for the agent.

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 covers basic purpose and required parameters, but lacks detail on the reorder effect, the exact meaning of the 'order' array, and the shape of the returned object (no output schema).

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 100%, so baseline is 3. The description merely repeats the required parameters without adding meaning beyond the schema, e.g., explaining the format or expected order of the 'order' array.

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 reorders company roles, with specific verb and resource. However, it does not explicitly differentiate from sibling tools like patch_company_role or post_company_role, and the phrase 'Creates a new Company Settings' introduces slight ambiguity about whether it creates or updates.

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 reordering but lacks explicit guidance on when to use this versus alternatives (e.g., updating a single role). No when-not-to-use or alternative tool names are provided.

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