appwrite_create_topic

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

No annotations provided, and description carries minimal behavioral context. While 'Create' implies mutation, there is no disclosure of idempotency behavior, error conditions (e.g., duplicate topic_id), or required permissions.

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?

Single sentence is appropriately brief, but front-loading '[UNIFIED]' wastes valuable description space without aiding agent comprehension.

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 4 parameters with no schema descriptions, no annotations, and no output schema, the description is insufficient. It fails to explain the Appwrite messaging domain or how topics relate to subscribers and messages.

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?

With 0% schema description coverage, the description must compensate but fails entirely. It does not explain what 'site' refers to (Appwrite project/instance), expected format for 'topic_id', or the purpose of the 'subscribe' parameter.

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 states a clear verb ('Create') and resource ('messaging topic'), distinguishing it from sibling operations like appwrite_delete_topic and appwrite_get_topic. However, the '[UNIFIED]' prefix adds noise without semantic value.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., appwrite_create_subscriber for adding subscribers to topics) or prerequisites for the 'site' parameter.

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