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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the OData endpoint and filter capabilities, but it does not disclose pagination behavior, return shape, or authentication requirements. This is acceptable but not rich.

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 no filler. It front-loads the verb and resource, then immediately provides the most relevant filtering options. Every word earns its place.

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?

With 8 parameters, no output schema, and sibling tools like legalone_get_users, the description is too minimal. It does not explain return values, pagination behavior, the query object, or how this tool differs from the get_users sibling, leaving significant gaps for an agent to choose and invoke it correctly.

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%, so the description must compensate for parameter meaning. It names five of eight parameters ($filter, $top, $skip, $orderby, $expand) but omits $select, $count, and query, and provides no syntax or format details beyond the parameter names.

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 ('Lista') and resource ('Usuários/responsáveis do escritório') and identifies the OData endpoint (/Users), making the core purpose clear. However, it does not distinguish this tool from the sibling legalone_get_users, which likely serves a similar or overlapping use case.

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 filtering guidance ('Filtre com $filter/$top/$skip/$orderby/$expand') but gives no explicit guidance on when to use this tool versus alternatives such as legalone_get_users or legalone_odata_get. There are no when-to-use or when-not-to-use instructions.

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