project_sync_projects_principals

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, so the safety profile is known. The description adds nothing beyond restating the endpoint: it does not say whether existing principal assignments are removed, whether the operation is asynchronous, or what privileges it requires. For a non-idempotent mutation this is a real gap.

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?

Very short and front-loaded, which is fine, but the second line merely duplicates the HTTP path already present in the title and annotations — it occupies space without earning it, and the first sentence is under-specified rather than tight.

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?

This is a non-idempotent mutation with no output schema and no explanation of effect, side effects, or result. Given the complexity of principal/role synchronization in an identity system, the description leaves too much for the agent to infer.

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%, so both parameters (id, apiVersion) are already documented in the schema and the baseline is 3. The description's '{id}' reference matches the schema without adding format, scope, or validation detail.

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?

States a verb ('sync') and a resource ('principals assigned to a project'), which is better than a tautology. But 'sync' is undefined — an agent cannot tell whether this pushes org-level principals down to the project, reconciles them bidirectionally, or replaces the assignment set. The sibling project_modify_project_principals is never differentiated.

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 when-to-use guidance, no prerequisites, and no mention of the obvious alternative project_modify_project_principals, which an agent would need to distinguish this from. The only context is the raw HTTP path.

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