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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description adds meaningful behavior beyond those annotations by stating that passwords and keys are never returned and by identifying the underlying GET /users endpoint. It does not mention pagination or rate limits, but the security-sensitive exclusion is a valuable disclosure.

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 three tight sentences with the core list operation front-loaded. Each sentence adds useful information: returned fields, the vendor_id relationship, sensitive-data exclusion, and endpoint.

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 zero-parameter, read-only listing tool with no output schema, the description provides enough detail to call it correctly: what is listed, which fields come back, how the id relates to sales, and what is intentionally omitted. Annotations cover the safety profile.

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?

The tool has zero parameters, so the schema itself is complete and no parameter guidance is required. The description appropriately spends no space on nonexistent inputs.

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: list Hiboutik users. It clarifies the user types (staff, sales vendors) and lists returned fields (id, name, email, access level), so an agent can distinguish this from the customer, product, and sale listing 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?

The description gives clear context by explaining that the returned id is the vendor_id used on a sale, which helps an agent know why to call it. It does not name explicit alternatives or when-not conditions, but there is no sibling user-listing tool to route against.

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