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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, but the description adds real context: the write is a sparse patch, it is built on the current profileRevision (optimistic concurrency), and creator direction plus selected references are preserved. The explicit disclaimers that a save is not approval, verification, generation, or publication are exactly the kind of semantic boundary annotations cannot express. It does not explain what a stale expected_revision produces or what a destructive overwrite of supplied fields clears, which keeps it below 5.

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?

Four short sentences, front-loaded with the action and followed by prerequisite, preservation rule, and scope boundary; no filler. The vocabulary ("sparse," "Brand direction," "Genfluencer persona") is domain jargon that assumes context, but each sentence carries information.

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 6-parameter mutation tool with nested objects and a destructive hint, the description covers the key preconditions and the read-before-write contract, and an output schema exists so return values need not be described. Still missing is conflict/error behavior on a stale revision and a clear statement of what a destructive save replaces versus preserves beyond the general preservation sentence.

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 50% schema description coverage, the schema documents operation_id, read_skills, expected_catalog_version, and publication_proposal_id, while the description adds meaning only for the patch ("sparse") and expected_revision (take it from the current profileRevision). The semantics of the large nested patch object — which fields belong to Brand direction versus Genfluencer persona, and whether omitted keys are cleared — are not explained in either place, so compensation is partial rather than complete.

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 gives a specific verb and resource ("Save a sparse Brand direction or Genfluencer persona patch to this studio") and scopes the write as a partial patch, which is more precise than the bare name or the title "Save direction." It stops short of naming a sibling it differs from (e.g. native.create_identity_project, native.organize_identity_documents), so an agent still has to infer the boundary from the identity-* family.

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?

It states a workflow prerequisite ("Read the identity profile and use its current profileRevision") and sets a negative boundary ("not approval, factual verification, generation, or publication"), which usefully prevents an agent from treating a save as a sign-off step. However, no alternative tool is named and no explicit condition says when to save versus creating a new identity project or organizing documents.

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