add_project_member

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. It only states the action, without mentioning idempotency, results for duplicate members, required permissions, or error conditions. This is a significant gap for a mutating operation.

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 exceptionally concise, leads with the primary purpose, and uses a clean Args block for parameters. Every sentence is purposeful and there is no redundancy or filler.

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?

The tool is a simple add operation, and the description covers the basic intent and parameter-sourcing hints. However, with no annotations and no mention of return behavior, idempotency, or permissions, the description leaves important contextual gaps that an agent would benefit from knowing.

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 must compensate. It adds useful hints for 'user_id' and 'role_ids' by pointing to list_users and list_roles, but 'project_identifier' is only restated as 'project identifier', providing no new meaning. This partial compensation supports a mid-range score.

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 uses the specific verb 'Add' and names the resource ('project member'), and clarifies that it involves 'one or more roles'. This makes it distinct from siblings like 'remove_project_member' and 'update_project_member', though it does not explicitly name those alternatives.

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 includes practical guidance by referencing 'use list_users' and 'use list_roles' for obtaining valid parameter values. However, it lacks explicit direction on when to use this tool instead of 'update_project_member' or 'remove_project_member', leaving the choice largely implicit.

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