List uStore API endpoints

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

With no annotations, the description carries the burden of indicating safety and behavior. 'List operations' conveys a read-only action and the filterable fields are stated, but it does not describe pagination behavior, output shape, or authentication expectations. This is acceptable for a simple list tool but not highly transparent.

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 with the key action first and filtering capabilities in the second. Every word earns its place; there is no repetition or filler.

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 discovery tool with four fully documented optional parameters and no output schema, the description is largely complete: it states the resource, the filtering dimensions, and implies the fields available in results. It does not add alternative-tool guidance, but given the low complexity, this is a minor gap.

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 baseline is 3. The description rephrases tag, method, and search filtering but adds little beyond the schema's parameter descriptions; the search field details are already present in the schema. The limit parameter is left entirely to 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 the tool lists operations in the uStore BackOffice REST API, with a specific verb and resource. It distinguishes itself from siblings like ustore_describe_endpoint, ustore_call_endpoint, and ustore_list_tags by focusing on discovering operations rather than describing, calling, or listing tags.

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 intended use is implied by the purpose — discover API operations and optionally filter them — but the description does not explicitly state when to prefer this tool over alternatives, nor does it mention excluded cases or prerequisites. There is no when/when-not guidance, only the clear listing behavior.

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