mgmt_delegate_create

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. It confirms that a delegate is created and gives the body shape, but it does not mention side effects, required permissions, idempotency, expected response, or error behavior.

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 compact and front-loaded with the action and API docs link, followed immediately by the essential body structure. There is no filler or redundant restating of the tool name.

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 create operation, the exact payload and docs URL give an agent enough to construct a basic request. However, with no annotations and no output schema, the description lacks guidance on authorization, return values, and failure modes, making it adequate but not fully complete.

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's `body` description is a generic JSON placeholder, so the description's exact body example `{"delegate": {"user_login": "..."}}` adds the real semantic meaning. The `pretty` parameter is already sufficiently described in the schema.

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 states a clear action ('Add delegate') on a specific resource, and the API docs URL adds useful context. It is distinguishable from sibling tools like mgmt_delegates_list and mgmt_delegate_delete by the verb, but it does not explicitly contrast itself with them.

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 about when to use this tool versus alternatives such as mgmt_delegates_list or mgmt_delegate_delete. The verb 'Add' implies creation, but prerequisites, authorization context, and conditions are not stated.

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