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

Annotations only supply destructiveHint=true and a title, so the description carries most of the burden. It delivers real value by disclosing the hidden side effect (the user is also enrolled in the group's courses) and the endpoint, and the 'WRITE' prefix aligns with destructiveHint. Missing: duplicate-membership behavior and whether removal is possible.

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?

One compact sentence front-loaded with the WRITE marker and the core action, followed by parameter guidance and the endpoint. Every clause carries information; nothing is wasted.

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 three-parameter write tool with no output schema and sparse annotations, the description covers action, side effect, parameter nuance, and endpoint. It stops short of covering error cases (already a member, invalid ids) or what the response contains.

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 all three params are documented, giving a baseline of 3. The note about enroll_to_courses adds the consequence (synchronous course enrollment) rather than just repeating the flag's type, but doesn't clarify defaults or behavior when omitted.

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 ('add an existing user to a group') plus the non-obvious consequence (enrollment in the group's courses). An agent can distinguish it from talentlms_create_user and talentlms_enroll_user_in_course because both the 'existing user' constraint and the group scope are explicit.

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?

'Add an existing user' implies the user must already exist, which is useful context, but the description never names the alternative tools (create_user, enroll_user_in_course) or states when-not to use it. Usage is implied rather than spelled out.

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