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

The annotations only flag destructiveHint=true; the description adds real value by leading with 'MUTATES YouCanBookMe data', naming the HTTP method/path, and clarifying that profileId travels in the path and is never placed in the body — a non-obvious behavioral detail. It stops short of covering failure modes or what the mutation returns.

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?

Front-loads the mutation warning and endpoint, then required fields, then the passthrough tip. Every clause carries information; nothing is padding despite the terse telegraphic style.

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 create tool with annotations present and a nested `fields` object, the description covers endpoint, required inputs, path-vs-body separation, and the passthrough escape hatch. With no output schema, one more line on what is returned (e.g., the created member id) would make it 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?

Schema coverage is 100%, so baseline is 3, but the description adds the merge semantics hint and concrete examples of which attributes belong in the `fields` passthrough (email, description, pic), helping an agent decide between typed params and the escape hatch.

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 ('adds a team member to a profile') and even gives the underlying endpoint POST /v1/profiles/{profileId}/teammembers/items, which unambiguously separates it from youcanbookme_update_team_member and youcanbookme_list_team_members.

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?

Gives concrete routing guidance by pointing at youcanbookme_list_available_accounts for obtaining a calendarId, and tells the agent to use `fields` for non-typed attributes. It never explicitly contrasts with youcanbookme_update_team_member, so the create-vs-update choice is only implied by the verb.

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