list_engagements

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

No annotations are provided, so the description carries the full burden. It never states that this is a read-only, non-mutating operation, nor mentions permissions, default ordering, or total-count behavior. 'List' implies read semantics, but that is left to inference rather than disclosed.

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 purpose is front-loaded in the first sentence and the Args block is a tight, scannable list with no filler. Nothing is padded, though the block is a little spartan compared to prose that would flow for an agent.

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?

Given seven optional parameters, an output schema that already defines the return shape, and no annotations, the description supplies the parameter detail needed to call it correctly. It does not address ordering or the relationship to other engagement-listing views, but the essentials for correct invocation are present.

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, and it does: it names all seven parameters and adds real meaning such as 'contains' semantics for name, the enumerated status values (Not Started, In Progress, Completed), the engagement_type values (Interactive, CI/CD), and 'Results per page (default 25)' for limit. Minor gaps remain (e.g., how offset interacts with total results).

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 opening sentence states a specific verb and resource ('List engagements') with the clarifying modifier 'with optional filters.' An agent can distinguish it from get_engagement/create_engagement/update_engagement by the plural-list form, though the description never names those siblings as alternatives.

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?

There is no explicit guidance on when to use this versus get_engagement (singular), list_products, or the engagement-note tools. It only says filters are optional, which describes the shape of the call, not the conditions that select it.

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