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 agent knows this is a safe read operation. The description adds the bulk execution behavior via 'grupo_ids', which is useful extra context. However, it does not disclose other behavioral aspects like pagination defaults or response format, which is acceptable given the 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 extremely concise, consisting of two sentences. It front-loads the core purpose and adds one key behavioral trait (bulk support). Every word earns its place with zero redundancy.

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 list tool with no output schema, the description is adequate but not exhaustive. It covers the primary purpose and bulk capability, but does not mention pagination, filtering, or any prerequisites. Given the annotations and sibling tools, this is minimally complete but lacks depth for agents unfamiliar with the pattern.

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 meanings. It only explains 'grupo_ids' for bulk support, but leaves 'page', 'page_size', 'query', and 'grupo_id' unexplained. For a list tool, these are likely pagination and filtering params, but the description does not add this clarity, providing limited semantic value.

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's purpose: 'Lista pessoas de um grupo' (list people of a group). The verb+resource is specific and distinguishes it from siblings like 'easyjur_list_pessoas' (which lists all people) and 'easyjur_list_grupos'. The mention of bulk support further clarifies functionality.

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 implies usage for listing people within a group, but does not explicitly state when to use it instead of other list tools (e.g., easyjur_list_pessoas). No exclusions or alternative tool references are provided, so usage guidance is only implicit through the name and context.

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