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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds useful context beyond that: the name validation rules, that it returns the new id, and the underlying POST route, which helps the agent understand what to expect back.

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?

Three short, front-loaded fragments with no filler; the operation type, constraint, and return value all appear immediately.

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 single-parameter create tool with rich annotations and no output schema, the description covers the name constraint and the returned id, which is enough to call it correctly. Only the duplicate-name/uniqueness behavior is missing.

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%, so the description must carry the parameter burden, and it does: it restates the 4-99 character limit and the allowed character set (letters, numbers, spaces, @ . _ -) in readable prose, matching the schema pattern. It does not explain whether names must be unique.

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?

States a specific verb and resource ("create a usergroup") and even names the endpoint. It is clearly distinguishable from siblings like get_usergroup or add_usergroup_member by the name itself, though it doesn't explicitly contrast with axislms_create_user.

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 "WRITE:" prefix signals it is a mutating operation, but there is no guidance on when to use this vs alternatives (e.g., to fetch an existing group use get_usergroup, to list use list_usergroups) and no prerequisites or duplicate-name behavior is mentioned.

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