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

Annotations already cover the operational safety profile with readOnlyHint=true and destructiveHint=false, so the description only needs to add behavioral context. It adds useful detail about the role vocabulary and the reference table, but it does not disclose return shape, behavior when no mapping exists, or any pagination/lookup properties. That is acceptable but not rich by the standard set by strong examples.

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 sentence with the action front-loaded and no redundant words. The list of deadline types at the end is information-dense, which slightly hurts readability but is justified because it previews the enum space.

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 two-parameter, read-only lookup with no output schema, the description covers the core semantics well: what input items are, what the tool will compute, and what vocabulary the answer uses. It could be strengthened with a note about edge cases like missing mappings, but nothing is critically absent for invoking 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?

Schema description coverage is 100%, so both parameters are already individually documented. The description adds meaning beyond the schema by stating the domain table (deadline_event_roles) and listing the role categories and deadline families, which helps an agent know what response to expect and how the two parameters interact.

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 identifies a specific verb—'Check what role'—and a clear resource: the deadline_event_roles vocabulary table mapping event codes to deadline role. It also lists the possible role outputs, which makes the tool's purpose very concrete. It stops short of a 5 because it does not explicitly differentiate itself from sibling lookup tools like get_event_code_reference or get_event_status_mapping.

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?

There is no guidance on when to use this tool versus the many sibling reference tools. The description implies the intended use case, but no alternatives, exclusions, or prerequisites are named, so an agent would need to infer the right choice from the tool name and purpose alone.

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