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

Annotations already declare readOnlyHint: false, idempotentHint: true, and destructiveHint: false. The description confirms these by stating 'Not read-only; it changes sharing permissions' (consistent) and 'is idempotent, so re-granting the same level is safe' (consistent). It adds value by explaining the idempotent behavior in plain language. No contradiction is present.

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 three sentences, each serving a clear purpose: stating the action, giving usage context, and noting behavioral traits (read-only status, idempotency). No redundant or unnecessary words.

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?

With 3 parameters, a clear description, and an output schema (though not shown), the description covers the core functionality. However, it misses context on potential side effects (e.g., notification sent to the user) or error conditions (e.g., if email does not match a valid user). The 'Not read-only' statement is useful but could be more precise.

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 the schema provides clear descriptions for all three parameters. The description adds no further detail on parameter values or format beyond what is already in the schema, which is acceptable per guidelines (baseline 3).

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 action: 'Grant a team member access to one of your ideas at a chosen access level (view, edit or admin).' It specifies the resource (idea), the recipient (team member by email), and the available access levels. This distinguishes it from siblings like 'create_share_link' (likely a different sharing mechanism) and 'update_idea' (which modifies content, not permissions).

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 says 'Use it to share an idea with a collaborator by email,' providing clear when-to-use guidance. However, it lacks explicit when-not-to-use instructions or alternatives for other sharing methods (e.g., a share link). It also does not clarify prerequisites (e.g., does the target user need an account?).

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