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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so no contradiction. The description adds the key behavioral detail that the store is initially empty and that files are added via a separate tool, but it doesn't mention any permissions, return values, or other side effects beyond the creation itself.

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 two short sentences: the first front-loads the tool's purpose and the second gives a direct follow-up tool reference. Every word serves a purpose and there is no fluff.

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 simple two-parameter creation tool with complete schema coverage and no output schema, the description is sufficient. It even points to the next step (ingest_file_to_store) to close the workflow loop. It doesn't explain how to retrieve the created store's ID, but that's not essential for invocation.

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%, so the schema already documents both parameters. The description does not add additional parameter semantics beyond saying it creates an empty store; it doesn't clarify how name or metadata are used beyond what the schema states.

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 specific verb and resource ('Create a new, empty vector store (knowledge base) in the org'), and it distinguishes itself from siblings like create_agent or attach_vector_store by specifying that it creates an empty store that is later populated via ingest_file_to_store.

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 clearly implies a workflow: create the store first, then ingest files using ingest_file_to_store. It provides context on when to use this tool, though it does not explicitly exclude alternatives like attach_vector_store for existing stores.

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