upsert_workspace_entity

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

With only readOnlyHint=false provided, the description carries most of the behavioral disclosure burden. It reveals that the operation can create/update and publish privately or as a DAO proposal, but it does not explain side effects of DAO publishing, required permissions or wallet state, reversibility, or failure behavior. No contradiction with annotations exists.

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 and front-loads the core upsert behavior. It is concise, though it sacrifices some helpful detail in favor of brevity for a tool with 14 parameters.

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 complex 14-parameter tool with no output schema and minimal annotations, yet the description only summarizes intent. An agent would not know how to construct a valid call differentiated by kind, when to supply entityId, how to publish as a DAO proposal, or what inputs are required for each mode.

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 only 29%, so the description should compensate for the 10 undocumented parameters. It adds context around kind (note/task/project) and visibility/publishing, but leaves many ambiguous fields unexplained: status values, dueDate format, noteType, priority, votingMode, daoSpaceAddress, and how entityId triggers update versus create.

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 an upsert (create/update) operation on workspace entities and scopes it to note/task/project kinds, with publishing behavior. It is specific enough to distinguish this from generic siblings like create_entity/update_entity, though it does not name them explicitly.

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 use this tool versus siblings such as create_entity, update_entity, propose_dao_edit, or publish_edit. The phrase 'or as a DAO proposal' hints at an alternative mode, but conditions, prerequisites, and exclusions are missing.

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