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

Annotations already declare this is a read-only, non-destructive, open-world operation. The description adds genuinely useful context beyond that: the segment is 'dynamic' (membership is computed, not a static list) and results are paged with limit/offset. It stops short of describing result shape or paging behavior in depth, but that is largely covered by structured fields.

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: capability and paging first, prerequisite routing second, endpoint last. Every clause carries information an agent can act on, with no 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?

There is no output schema, but the offset parameter documents passing the previous reply's next_offset, which implies the paged response shape, and annotations cover the safety profile. Fairly complete for a read-only list tool, though return-field behavior is only lightly touched.

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 100%, so every parameter is already documented with type, bounds, and defaults. The description only paraphrases paging, sort, and field selection without adding format or syntax detail beyond what the schema provides, matching the baseline 3 when the schema does the heavy lifting.

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 names the resource (people in one dynamic segment) and scope clearly, and routes to sibling tools for segment ids and field names, so an agent can distinguish it from encharge_list_segments and encharge_list_fields. The verb is implied rather than stated, but the title and resource make the operation unambiguous.

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?

It explicitly tells the agent where to get prerequisites: encharge_list_segments for segment ids and encharge_list_fields for field names. It does not, however, address when to use this versus encharge_get_people, the closest alternative, so the routing is helpful but incomplete.

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