tc_grant_permissions

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

The description fully discloses the merge behavior: reads the current ACL, moves given subjects to the requested level, and writes the whole ACL back while preserving everyone else's permissions. It also notes the folder-only restriction for 'NO_ACCESS' and the TC_ENABLE_WRITE=1 requirement, all of which go beyond the annotations.

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 well-structured and front-loaded: a one-line summary, a behavioral explanation, a prerequisite, then an Args list, and a Returns line. Every sentence provides necessary information, and the Args list is compact yet complete.

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 tool with 6 parameters, no schema descriptions, and an output schema, the description covers everything needed: the action, mechanism, prerequisites, parameter semantics, and return value shape. It provides enough detail for an AI agent to invoke it correctly without additional lookup.

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 compensates elegantly by explaining each parameter: subject_ids with a special wildcard, level with allowed values and folder-only restriction, item_type with default, inheritance with optional behavior, and project_id/item_id as identifiers. This is essential for correct invocation.

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 starts with a specific verb ('Give') and resource ('users/groups a permission level on a folder or file'). The parenthetical '(safe merge)' immediately distinguishes it from siblings like tc_set_permissions and tc_remove_permissions by hinting at the merge behavior.

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 clearly states the operation's context and a critical prerequisite (TC_ENABLE_WRITE=1). It also references sibling tools (tc_list_project_members, tc_list_groups) for constructing subject_ids. However, it does not explicitly say 'use this instead of tc_set_permissions' or otherwise contrast with alternatives.

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