update_topic_directory

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

With no annotations, the description must carry the behavioral load; it does disclose partial-update semantics ('unspecified fields remain unchanged'), which is genuinely useful for a mutation tool. It does not say what permissions are needed, whether moving a folder is recursive, or how collisions/duplicate names are handled.

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 short sentences with the action front-loaded and the partial-update caveat second; nothing is wasted. It is sparse rather than bloated, and the brevity is appropriate even if the content is thin.

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 4-parameter mutation tool with no annotations and no output schema, the description omits the identity semantics of topic_id/directory_id and any error or permission behavior. What is present is accurate, but not enough for an agent to call it confidently.

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%, so the description must compensate, and it only implicitly maps 'rename' to name and 'move' to parent_id. It never explains what directory_id versus topic_id means or why both are required, leaving the two mandatory parameters undocumented in both places.

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?

States a specific verb pair (rename/move) and a specific resource (knowledge-base folder), which clearly separates it from the sibling create_topic_directory, delete_topic_directory and list_topic_directories. It does not name those siblings explicitly, but the action scope is unambiguous.

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 verbs 'rename or move' imply when to use the tool, and the second sentence tells the caller that unspecified fields stay unchanged. There is no explicit statement of when NOT to use it or which sibling to pick for creation/deletion, so usage is only implied.

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