Add project member

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

Annotations already state readOnlyHint=false and destructiveHint=false, so the safety profile is covered. However, the description adds no extra behavioral context (e.g., whether it replaces existing membership, requires project owner permissions, or returns the created member). It merely restates the tool's purpose without disclosing side effects.

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 a single concise sentence ('Grants a user access to a project.') with no fluff. It is appropriately front-loaded and easy to parse, though it could include a bit more detail without becoming verbose.

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 the simplicity of the tool, the description is adequate but has gaps. There is no output schema, so the agent does not know what the tool returns (e.g., the created membership object). The annotations and schema cover safety and parameters, but behavioral aspects like idempotency or permission requirements are missing.

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% with descriptions for all four parameters (user_id, access_level, expires_at, project_id). The description itself does not add parameter-level meaning, so the baseline of 3 applies. The access_level description in the schema is explicit about numeric values.

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 'Grants a user access to a project' uses a specific verb ('grants') and identifies the resource (project access). It clearly conveys the tool adds a member, though it could be more explicit about 'adding a project member' or 'access level'. It is distinct from sibling tools like list_project_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?

No guidance is provided on when to use this tool versus alternatives (e.g., list_project_members, update_project_member). The description does not mention prerequisites, exclusions, or context. The agent is left to infer from the name and siblings.

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