engagement_status

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says 'show' which implies a read-only operation, but it does not disclose what happens when no active engagement exists, whether the findings summary includes counts or full details, or how the result is structured. With zero annotations and no output schema, this is a significant gap.

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, front-loaded sentence that directly states the purpose. There is no fluff or redundant detail—every word earns its place. This is an example of excellent conciseness.

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 that this is a simple status tool with no parameters, the description is minimally sufficient. However, the lack of an output schema and annotations means the description should clarify the expected return value (e.g., what exactly a 'findings summary' contains) and edge cases like no active engagement. It's adequate but has clear gaps for an agent to fully understand the tool's behavior.

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 tool has zero parameters, and the schema description coverage is 100% (vacuously). The description adds no ambiguity because there are no parameters to explain. According to the rubric, 0 parameters warrants a baseline 4, and the description does not introduce any confusion.

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 function: showing the current active engagement and its findings summary. It uses a specific verb ('show') and resource ('current active engagement'), which distinguishes it from vague tools. However, it doesn't explicitly differentiate itself from sibling tools like engagement_findings or get_findings, so it's not a perfect 5.

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. There is no mention of scenarios where this tool is preferred, nor exclusions for when to use engagement_findings or get_findings. The agent is left to infer usage from the tool's name and simple description.

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