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

Annotations provide minimal behavioral hints (readOnlyHint=false). The description adds that team.memberCount stays in sync and mentions 'host' at the end, implying authorization requirements but not explicitly. It does not discuss rate limits, reversibility, or detailed side effects beyond the count sync.

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 dense and front-loaded with the main purpose, followed by entity-relation mappings. It avoids fluff but could be more structured (e.g., bullet points) to improve readability. Every sentence adds value, though the final 'host' fragment is somewhat ambiguous.

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?

Given six required parameters, no output schema, and sparse annotations, the description covers core usage and entity mappings but omits return value, error handling, and authentication details. It is sufficient for a user familiar with the domain but lacks completeness for an AI agent needing clear expectations.

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?

With 0% schema description coverage, the description adds significant context: it lists entity types and their corresponding relations, explains member identification (mode_id or name), and notes the op enum values. However, it does not elaborate on event_id, item_id, or the specifics of the member object (e.g., format constraints).

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 assigns a person to a production item, and provides explicit mappings of entity types to their roles (e.g., teams->members/leads). This distinguishes it from sibling tools like 'add_guest' or 'invite_team_member' which operate on different resources.

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 explains how to identify the member (by mode_id or name) and the operations (set/add/remove). It mentions synchronization of team.memberCount and required parameters. However, it does not explicitly state when to use this tool over alternatives like 'add_profile_member' or 'remove_community_member', leaving some ambiguity.

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