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

With no annotations, the description carries the full burden and it does reveal key behavior: the edit is immediate, human-authored, limited to one field, and system or agent changes are not permitted. It stops short of disclosing whether the existing value is overwritten, whether the change is reversible, or what the response looks like, but the most critical governance behavior is clearly stated.

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 two short sentences with no filler. The main action and immediate/human constraint are front-loaded, and the second sentence earns its place by adding an essential exclusion. Every word contributes to correct tool selection.

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?

The schema is simple, but there are no annotations and no output schema, so the description needed to explain parameter meaning and side effects. It explains the high-level routing decision well but leaves targetField semantics, value expectations, and post-edit behavior unspecified, making the overall picture incomplete for an agent that must actually invoke it.

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 0%, so the description needed to compensate for the schema's silence, but it does not. It never mentions targetField or value, does not explain the three allowed field names, and gives no guidance on how value should be formatted. The phrase 'one field' is the only implicit hint and is insufficient.

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 ('Apply') with a clear resource ('Knowledge Profile field') and a precise scope ('one field'). It also distinguishes itself from proposal-based updates by saying the edit is immediate and human-authored, which separates it from siblings like review_knowledge_proposal.

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 explicitly states when to use the tool ('immediate human-authored edit') and when not to ('System and agent changes must still use proposals'). This gives the agent a clear exclusion rule and points to the proposal workflow as the alternative, even without naming the sibling tool directly.

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