get_deadlocks

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 disclosing behavior. It only says 'get recent deadlock events' and does not explain whether it is read-only, what the return format is, how 'recent' is defined, or any permission requirements. This thin description does not meet the baseline for a tool with zero annotation support.

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 with no wasted words. It conveys the essential purpose without any fluff, making it easy to parse quickly.

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?

With no output schema, the description should explain what the tool returns (e.g., format, time range). It does not mention the output format or define 'recent', which could cause an agent to make incorrect assumptions. However, the tool's complexity is low, so the gap is moderate rather than severe.

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 only parameter 'server' is fully described in the input schema ('Target server name (uses default if omitted)'). The tool description adds nothing about parameters, but since schema coverage is 100%, the baseline of 3 applies.

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 a specific verb ('get'), a resource ('deadlock events'), and the source ('system_health Extended Events session'). This unambiguously distinguishes it from all siblings, none of which target deadlocks. An agent knows exactly what this tool retrieves.

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 context is clear: use this to obtain deadlock events. No exclusions or alternatives are explicitly mentioned, but none of the siblings provide equivalent functionality, so the usage is fairly obvious. It lacks an explicit 'when not to use' but is sufficient for selection.

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