plur_stores_add

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

Annotations indicate idempotentHint=true and destructiveHint=false. The description confirms idempotency by stating returns 'added' or 'already_registered'. It also explains that remote URLs can host multiple scopes and that each registration is independent, adding context beyond annotations.

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 concise with two sentences, front-loaded with the core purpose. It efficiently covers both registration types, usage pattern, and return status without unnecessary details.

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?

Given the absence of an output schema, the description adequately mentions the return status ('added' or 'already_registered'). It covers the 6 parameters sufficiently in context, though more detail on the 'shared' and 'readonly' parameters could be beneficial. Overall, it provides enough information for an agent to use the tool correctly alongside the sibling tools.

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 coverage is 100%, baseline 3. The description adds value by explaining the relationship between url+token vs path, and that 'one remote URL can host multiple scopes — call once per team scope'. It also mentions that shared indicates git-committed/team-visible and readonly for purchased packs, enhancing semantics beyond the schema.

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 'Register an additional engram store' with specific distinction between filesystem (path) and remote (url+token) stores. It also explains that one remote URL can host multiple scopes, differentiating this tool from siblings like plur_stores_list.

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 specific guidance on when to call the tool: 'call once per team scope you are authorized for' for remote URLs. It implies that this tool is for adding new stores, not for listing or other operations. However, it does not explicitly mention when not to use it or compare to other tools.

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