appflowy_set_publish_namespace

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

No annotations are present, so the description must convey all behavioral traits. It only states 'Rename', implying a mutation, but does not disclose side effects, authorization needs, constraints (e.g., namespace uniqueness), or impact on published pages.

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, which is too brief to be useful. It lacks essential details and is underspecified rather than concise. Every sentence should earn its place, but here the sentence is insufficient.

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 lack of annotations, output schema, and parameter descriptions, the description is seriously incomplete. It does not cover return values, error conditions, or operational constraints, making it hard for an agent to use 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 the two parameters: 'workspace_id' and 'new_namespace'. It adds no meaning beyond what the names suggest, leaving the agent without details on format, length, or required values.

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 the verb 'Rename' and specifies the resource 'workspace publish namespace', making it clear that this tool changes the publish namespace. It distinguishes from the sibling 'appflowy_get_publish_namespace' which reads the namespace, so purpose is clear.

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?

No guidance is provided on when to use this tool versus alternatives like 'appflowy_get_publish_namespace' or other publishing tools. There is no mention of prerequisites or context for renaming the namespace.

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