Create project team member

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the mutation/safety profile is covered structurally. The description adds the write-scope requirement, which is real value beyond annotations. It still omits what happens on a duplicate membership or whether the response returns the created record.

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?

Two short sentences with zero filler; the action is front-loaded and the authorization constraint follows immediately. Nothing could be removed without losing information.

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 seven-parameter mutation tool with no output schema, the definition covers the action and the auth requirement but says nothing about the result of the call or edge cases such as an already-existing member. Adequate as a minimum viable definition, but thin for the tool's complexity.

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% and all seven properties carry descriptions, so the schema already documents role, user_id, project_id, dates, and responsibilities. The description adds no parameter-level meaning (e.g. role vocabulary, date semantics, default for is_active), so the baseline 3 applies.

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 a team member to a project'), which is unambiguous against siblings like create_project, create_project_task, or update_project_team_member. It does not explicitly name a sibling alternative, but the name-plus-description pairing makes the target entity clear without opening the schema.

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 names the required authorization scope (project_team_members:write), which is a genuine usage prerequisite an agent must satisfy before calling. It gives no guidance on when to prefer this over bulk_create or update_project_team_member, and no exclusions, so usage is only implied.

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