create_topic

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

With no annotations provided, the description carries the full disclosure burden. It valuably specifies the rate limit (50/day) and reset time (00:00 Beijing time), but omits mutation behavior details like idempotency, error handling when limits are exceeded, or whether creation is synchronous.

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 consists of two efficient sentences: the first establishes purpose, the second provides the critical constraint. Zero wasted words; information is front-loaded.

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 creation tool with 3 simple parameters and no output schema, the description covers the essential constraint (rate limiting) but leaves gaps regarding return values, success confirmation, or error scenarios.

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%, establishing a baseline of 3. The description text adds no parameter-specific guidance beyond what the schema already provides (name, description, cover).

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 '创建新的知识库' (Create new knowledge base), providing a specific verb and resource. It implicitly clarifies that 'topic' in the tool name maps to 'knowledge base' in the domain model, distinguishing it from note-centric siblings like save_note or list_notes.

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?

The description provides a rate limit warning but offers no guidance on when to use this tool versus alternatives like list_topics (to check for existing topics before creating), nor prerequisites such as uniqueness constraints.

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