accounts.upsert

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

With no annotations, the description carries the full behavioral burden. It says 'create or update' but never states what happens on conflict, whether the write touches the on-disk registry file (implying persistence), whether a reload is required for changes to take effect, or what permissions/auth the write needs. These are meaningful gaps 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?

One short, front-loaded sentence with zero filler and the verb+resource stated immediately. It is arguably too terse for the operation's complexity, but on the conciseness axis it is essentially optimal.

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 mutation tool with no annotations and no output schema, the description omits critical context: whether the change persists to the registry file, whether the in-memory registry must be reloaded (a sibling exists), and what the tool returns. An agent could invoke it, but not confidently.

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 every parameter is already documented, including the patch-vs-replace semantics of 'replace' and the meaning of 'account_id'. The description adds no parameter-level detail beyond the schema, so the baseline 3 applies.

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 specific verb pair (create or update) and resource (project profile in the accounts registry file), which is clear and distinguishable from siblings like accounts.delete and accounts.list. It does not explicitly position itself against accounts.reload or the other accounts tools, so it stops short of a 5.

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?

There is no guidance on when to prefer upsert over accounting operations like accounts.reload, nor any note about preconditions such as the registry needing to exist or be reloaded afterward. The only usage signal is the word 'upsert' in the name, which the description merely restates.

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