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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), so the description's main addition is the endpoint path and the returned fields. It says nothing about pagination behavior, default page size, or that results are state-filterable, which an agent listing many users would want to know.

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?

Two compact sentences, front-loaded with the purpose. The trailing endpoint path is mild filler but cheap and occasionally useful for debugging.

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 read-only five-parameter list tool with no output schema, the description tells the agent what fields come back, which is genuinely useful. But it omits the paging contract and filtering options that determine correct invocation, leaving gaps the schema only partially fills.

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 only 60% and the description contributes zero parameter meaning: it never mentions limit/offset paging, the state filter, office_id scoping, or expand. The two undocumented params (expand, office_id) are left entirely unexplained anywhere.

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?

States a specific verb and resource ('List Bsale users') and disambiguates the resource as sellers/cashiers, plus what fields come back (name, office). No explicit differentiation from the nearest sibling bsale_user_sales_summary, but the resource noun is distinctive enough.

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?

No when-to-use guidance, no prerequisites, no mention of how it relates to bsale_user_sales_summary or bsale_list_offices, despite office_id being a filter. The agent must infer that this is a plain roster lookup.

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