list_engagements

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

The description discloses that the tool lists engagements (a read operation), but it does not elaborate on side effects, permissions, or whether it returns all engagements globally or scoped to a user. With no annotations, the description carries the burden and leaves some ambiguity about scope and pagination.

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 a single, well-structured sentence that front-loads the core action and filtering option. There is no wasted text, and it is immediately scannable.

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 operation with one optional parameter and an existing output schema, the description covers the key filtering behavior. However, it lacks details on output scope (e.g., whether it lists all engagements globally or per user) and pagination. Still, it is largely sufficient for an agent to decide to invoke the tool.

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?

The parameter 'status' has 0% schema description coverage, so the description entirely compensates by stating it can be 'active' or 'closed', effectively providing enum values. This gives the agent all necessary semantic information to use the parameter correctly.

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 action ('List all engagements') with an optional filter. It distinguishes itself from sibling tools like 'get_engagement' (single) and 'create_engagement' (create), making its purpose 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?

No explicit guidance is provided on when to use this tool versus alternatives such as 'get_engagement' for individual records or 'close_engagement' for updates. The usage is only implied by the listing action, but the description lacks when-not-to-use or alternative mentions.

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