update_entity_settings

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the action ('Update access settings') but does not disclose side effects, whether settings are replaced or merged, required permissions, or the potentially destructive nature of changing access controls. This is a significant gap for a mutation tool.

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, focused sentence that immediately states the action and target. It is front-loaded, easy to parse, and contains no unnecessary words or repetition.

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?

Despite having complete parameter schemas and an output schema, the description lacks critical behavioral context for a security-sensitive mutation tool. It does not explain whether the update is additive or replaces existing settings, what permissions are required, or what impact it has on users. This makes the description inadequate for safe invocation.

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?

The schema provides descriptions for all four parameters, so the baseline is 3. The description adds no additional meaning beyond grouping acl and permission_sources as 'access settings', which is already evident from the parameter names. It does not enhance parameter understanding.

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 a specific verb ('Update') and resource ('access settings'), and explicitly lists the supported entity types (project, portfolio, goal). This clearly differentiates it from sibling tools like update_entity (general entity fields) and get_entity_settings (retrieval).

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. There is no mention of prerequisites, exclusions, or scenarios where this tool is preferred over update_entity or other permission-related tools. Usage is only implied by the description, not explicit.

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