engagement_details_get

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

No annotations are provided, so the description carries full burden. 'Get details' implies a read operation, but it doesn't disclose whether this requires authentication, has rate limits, returns structured data or raw content, or what happens if the engagement doesn't exist. For a tool with zero annotation coverage, this leaves critical behavioral aspects unspecified.

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, efficient sentence that gets straight to the point with no wasted words. It's appropriately sized for a simple retrieval tool and front-loads the core action.

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 the complexity (a read operation with no annotations, 0% schema coverage, and no output schema), the description is insufficient. It doesn't explain what 'details' includes, how results are structured, or error conditions. For a tool in a rich ecosystem with many siblings, this leaves too much undefined for reliable agent use.

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 schema only indicates 'engagementId' is required without explaining what format it expects. The description adds no parameter details beyond implying an engagement ID is needed. Since there's only one parameter, the baseline is 4, but the description doesn't compensate for the coverage gap, so 3 is appropriate.

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 purpose understandable. However, it doesn't differentiate from sibling tools like 'engagement_details_get_associated' or 'engagement_details_list', which would require more specificity about what 'details' means in this context.

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 provides no guidance on when to use this tool versus alternatives. With siblings like 'engagement_details_get_associated' and 'engagement_details_list', there's no indication whether this tool retrieves basic metadata, full records, or something else, leaving the agent to guess based on naming patterns alone.

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