Add Store

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

With zero annotations, the description carries the full burden of behavioral disclosure. It adds one useful behavioral fact (no restart required), but omits what happens on duplicate names, whether registration validates connectivity to the store, whether it persists, and what side effects occur beyond registration.

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 single sentence is front-loaded and wastes no words, which is good. However, it is under-specified for a 12-parameter, 3-kind tool; conciseness here crosses into insufficiency rather than appropriate brevity.

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?

Despite the output schema covering return values, the description is far from complete for a tool with 12 parameters, 3 store kinds, and no annotations. An agent cannot determine which optional parameters are required for each store kind or how the fields interact.

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% with 12 parameters, so the description must compensate by explaining parameter meaning, but it names none of them. It does not clarify that url/path apply to git/directory while bucket/prefix/region/endpoint/access_key/secret_key apply to S3, leaving the agent to guess the per-kind parameter mapping.

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 uses a specific verb ('Register') with a concrete resource ('a directory, Git, or S3 store') and adds a useful qualifier ('without a restart'). The three store kinds help distinguish it from sibling tools like remove_store and update_store by implying creation semantics, though it never explicitly contrasts itself with those siblings.

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?

There is no guidance on when to use add_store versus update_store, refresh_store, or migrate_store, and no conditions or prerequisites for registering a store. 'Without a restart' implies a hot-registration benefit but does not tell the agent when this tool is the right choice.

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