appwrite_list_topics

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

No annotations provided, so description carries full burden. It successfully explains what topics are (subscriber groups), providing necessary domain context. However, it lacks technical behavioral details like pagination, rate limits, or return value structure.

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?

Two sentences with efficient structure. The '[UNIFIED]' prefix is unnecessary noise but brief. The first sentence states the action; the second provides valuable domain context without waste.

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?

Adequate for a simple list operation - it explains the resource being listed. However, with 3 undocumented parameters and no output schema, the description should have included parameter guidance or filtering syntax to be fully complete.

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 fails to compensate for undocumented parameters. It mentions neither the required 'site' parameter nor explains the 'queries' and 'search' filtering options, leaving all 3 parameters effectively undocumented.

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 the verb 'List' and resource 'messaging topics', and distinguishes from siblings like appwrite_get_topic (single) and appwrite_list_messages (different resource). The explanation that 'Topics are groups for sending messages to multiple subscribers' clarifies the domain concept effectively.

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 explicit guidance on when to use this versus appwrite_get_topic or when to use the filtering parameters (queries/search). The phrase 'List all' suggests unfiltered retrieval but doesn't explain how to use the optional query parameters for filtering.

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