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

With no annotations provided, the description carries the burden of behavioral disclosure. It does mention the need for operator-class credentials and the add/supersede action, but it omits details about side effects of superseding, reversibility, or idempotency, leaving important behavioral traits undisclosed.

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 sentence with no filler, but it is slightly dense and the phrase 'by the API' is redundant. Overall, it is efficient but could be clearer in structure.

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?

Given the tool's complexity (7 parameters, nested objects, output schema), the description is far too sparse. It fails to address parameter semantics, return values, or any usage prerequisites beyond credentials, making it inadequate for an agent to invoke correctly.

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%, and the description does not explain any of the 7 parameters. Cryptic fields like 'situation_fingerprint' and 'expected_sufficiency_min/max' are left undefined, forcing the agent to guess their meaning.

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 clearly states a specific action ('Adds or supersedes') on a specific resource ('AgentCharacterKernel'), making the tool's purpose obvious. It also highlights the privileged nature, distinguishing it from general access tools like get_character_kernel.

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 implies usage is restricted to privileged curation and notes that operator-class credentials are required, but it does not explicitly contrast with alternatives like submit_correction or update_constraint, nor does it provide clear 'when to use' guidance beyond the privileged context.

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