engagement_details_get

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

With no annotations provided, the description carries full burden for behavioral disclosure. It implies a read-only operation ('Get'), but doesn't specify authentication needs, rate limits, error conditions, or what the return format looks like (since no output schema exists). This is inadequate for a tool with potential complexity in data retrieval.

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, straightforward sentence with no wasted words, making it easy to parse. However, it's arguably too concise given the lack of supporting annotations and schema descriptions, bordering on under-specification rather than optimal brevity.

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 tool with no annotations, 0% schema description coverage, and no output schema, the description is insufficient. It doesn't explain what 'details' entail, how to handle errors, or provide usage context, leaving critical gaps for an AI agent to operate effectively in a complex environment with many sibling tools.

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 schema description coverage is 0%, so the description must compensate for parameter documentation. It mentions 'a specific engagement' which hints at the 'engagementId' parameter, but provides no details on format, constraints, or where to obtain it. This adds minimal value beyond the bare schema, failing to address the coverage gap.

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 'Get details of a specific engagement' clearly states the verb ('Get') and resource ('engagement'), making the basic purpose understandable. However, it lacks specificity about what 'details' include and doesn't differentiate from sibling tools like 'engagement_details_list' or 'engagement_details_get_associated', leaving ambiguity about scope.

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 guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an engagement ID), exclusions, or comparisons to sibling tools like 'engagement_details_list' for multiple engagements or 'engagement_details_get_associated' for related data, leaving the agent to infer usage context.

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