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

Annotations already declare this as a safe, idempotent, non-destructive read, so the safety profile is covered. The description goes beyond them by disclosing the output format (.ics), the one-event-per-timed-deadline structure, and the fixed 15-minute reminder offset, which is genuinely useful behavioral detail for a tool with no output schema. It stops short of saying whether the file is returned inline or as a download reference.

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?

A single tight sentence with no filler, and the artifact is front-loaded. It is a noun phrase rather than a verb-led statement of action, which slightly weakens the opening but wastes nothing.

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 correctly carries the burden of explaining the return value, and it does so well (event-per-deadline, reminder offset, import targets). What is missing is the relationship to the najjab_deadlines sibling and the delivery mechanism, but for a read-only generation tool the essentials are present.

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% across all 8 parameters, so the enum values, defaults, country codes, and ISO 8601 format are already fully documented in the schema. The description adds no parameter-level meaning, which is acceptable here but earns only the baseline.

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 names a concrete artifact (an iCalendar .ics file) and specifies its contents: one event per timed deadline plus a 15-minute reminder. That is far more than a restatement of the title, but it never distinguishes this tool from the sibling najjab_deadlines, so an agent cannot tell from the text alone whether this returns the same deadlines in a different format.

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 phrase 'ready to import into Outlook, Google Calendar or Apple Calendar' hints at a calendar-integration use case, but there is no explicit when-to-use, no when-not-to-use, and no pointer to najjab_deadlines as the alternative for reading deadlines in text form. The agent must infer the routing decision.

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

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed world). The description adds real behavioral context beyond them: results are ordered soonest first, due times are computed from the discovery time, follow-up updates and closure reports are included, and the answer changes with the severity grade. Return format/limits are not stated, so 4 not 5.

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 core output is front-loaded ('Every notification duty an incident triggers across the given countries, soonest first') and each clause conveys distinct information. It is one dense run-on sentence, which slightly hurts readability but contains no filler.

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 9 parameters, no output schema, and strong annotations, the description does the important work of describing the return shape (duties, ordering, computed dues, severity-conditioned notes). Remaining gaps, such as how zones or sector alter results and output formatting, are largely covered by the schema's parameter descriptions.

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 coverage is 100% with rich enum descriptions, so the baseline is 3. The description adds interpretation beyond the schema by explaining that due times derive from discovered_at and that severity/grade conditionally alters the output, clarifying how parameters drive results.

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 resource returned: every notification duty an incident triggers across given countries, with deadlines computed from discovery time. It is distinguishable from siblings like najjab_list_obligations or najjab_calendar because it is derived from an incident and computed rather than a static list. It stops short of naming a sibling it replaces, so it earns a 4 rather than a 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?

Usage is implied by the scenario: an incident has occurred and you need its resulting deadlines. There is no explicit when-to-use/when-not, no prerequisites, and no routing to alternatives such as najjab_playbook or najjab_calendar, leaving the agent to infer the right moment to call it.

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the agent knows this is a safe, repeatable, local generation call. The description adds useful framing (bilingual output, fact-gathering scope, authority-specific form/channel), but discloses nothing about authentication, rate limits, or the shape/size of the returned draft. No contradiction with annotations.

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?

Two tight sentences with the deliverable front-loaded and no filler. It is efficient, though slightly abstract for a 15-parameter tool where a few more words could have disambiguated the free-text fields.

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 15 parameters, 53% schema coverage, no output schema, and seven undocumented free-text inputs, the description carries a real burden. It explains the intent and the addressee but never describes what the drafted notice contains or how the unlabeled fields feed it, leaving a meaningful gap for an agent assembling a call.

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 only 53%, and the undocumented fields (actions, contact, records, summary, systems, organization, next_update) are bare strings with no guidance. The description partially compensates by framing these as "the facts every regulator asks for first," and the Arabic/English and authority mentions echo the lang and countries parameters, but it adds no syntax or format detail.

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 states a concrete deliverable (a plain notice, in Arabic or English) that consolidates the facts regulators ask for, addressed to the authorities an incident triggers. An agent can tell this is a drafting/generation tool. It never contrasts itself with the playbook, tabletop, or deadlines siblings, so differentiation is left to inference.

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?

"Addressed to the authorities the incident triggers" implies the context (post-incident notification) and "use the authority's own form and channel where one exists" gives downstream usage guidance. However, no sibling alternative is named and no when-not condition is stated, so selection guidance is only implied.

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

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value by enumerating the returned content (deadline rows, summary, official source with reference and link, secondary sources fallback), which matters because there is no output schema.

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?

A single front-loaded sentence that leads with the core action ('One duty by id') and then lists the return payload. No filler or repetition of the title.

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 does the work of explaining what comes back, including the secondary-sources fallback case. Language and format behavior are left to the schema, which is reasonable, so nothing essential is missing for correct invocation.

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 id, lang and response_format are already documented, and the baseline is 3. The description adds only extra id examples ('kw-cbk-incident', 'sa-sdaia-pdb') beyond the schema's 'qa-ncsa-nia', which is marginal added meaning.

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?

States a specific verb and resource ('One duty by id') plus the payload it returns, so an agent can tell it apart from najjab_list_obligations or najjab_deadlines. It stops short of naming those siblings explicitly, so differentiation is inferred rather than stated.

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 singular 'One duty by id' implies a single-record lookup as opposed to the list sibling, but there is no explicit when-to-use/when-not guidance or named alternative. Usage is left to inference from the name and description.

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

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: it is paged, and it discloses the shape of each returned record (authority, applicability, deadline in words, source, verification level) even though no output schema exists.

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?

Three tight sentences with no filler: the resource and return contents lead, filtering follows, paging closes. Every clause earns its place and nothing is repeated from the schema.

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 an eight-parameter, zero-required list tool with no output schema, the description compensates well by describing returned fields, filter axes and paging. It omits any mention of the lang/response_format switches and default filter behavior, which are minor given the schema documents them.

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 coverage is already 88%, so the schema carries most parameter meaning. The description still adds interpretive value by glossing 'zone' as 'financial free zone' (clarifying the difc/adgm/qfc enum) and by naming the two trigger semantics (cyber-incident or personal-data-breach), which the schema leaves as bare enum values.

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 names the resource (notification duties in the register) and enumerates the returned fields — authority, applicability, deadline in words, official source, verification level — so an agent knows exactly what a call yields. It does not explicitly differentiate itself from the singular sibling najjab_get_obligation, but the plural register-listing framing and filter surface make the distinction inferable.

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?

It states the available filters (country, financial free zone, trigger, sector) and that results are paged, which implies the browse-and-filter use case. However, it never says when to prefer this over najjab_deadlines or najjab_get_obligation, nor when-not to use it, leaving routing between siblings to inference.

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed world, so the safety profile is fully covered by structured data. The description adds content scope (what domains the overview spans) but says nothing about output size, pagination, or latency, so it adds moderate rather than rich behavioral context.

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?

A single colon-delimited sentence enumerating the covered domains, followed by the two-word directive 'Start here.' It is tightly front-loaded with no filler. The enumeration is a touch list-like, but every item conveys scope information the agent needs.

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 zero-required-parameter, read-only orientation tool, the description communicates the scope of the answer, and the two formatting parameters are fully specified in the schema. With no output schema, describing the subject matter of the response is the right substitute; only a note on response size or structure is absent.

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%: both 'lang' and 'response_format' are fully documented with enums and defaults, and the description adds nothing about them. Per the rubric, full schema coverage establishes a 3 baseline even with no parameter discussion in the description.

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 names the resource precisely — coverage of the six Gulf countries, the authorities and duties register, verification status — so an agent knows this is an orientation/summary tool. It does not explicitly contrast itself with siblings like najjab_list_obligations, so it falls short of a 5, but the verb-less 'what Najjab covers' framing is unambiguous about the content returned.

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?

'Start here' is an explicit, front-loaded usage directive that tells the agent to call this before the more specific siblings (list_obligations, get_obligation, deadlines, etc.). It gives no when-not or exclusion conditions, which keeps it from a 5, but the intended entry-point role is clear.

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

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the full safety and side-effect profile is covered structurally. The description adds no further behavioral context (no auth needs, no rate limits, no output length/format caveats), but for a read-only, idempotent content lookup there is little behavior left to disclose, so this is adequate rather than deficient.

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?

A single sentence that front-loads the resource and then enumerates scope in a compact, comma-separated list with zero filler. Every clause earns its place by describing a section of the returned playbook.

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 compensates by listing the playbook's sections, so the agent knows what it will receive and in what sequence. All inputs are fully documented in the schema with defaults. Only the missing routing guidance against sibling content tools keeps this from being fully complete.

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% and all three parameters carry enum descriptions plus defaults, so the schema does the heavy lifting. The description contributes only the phrase 'for an incident type', which adds no meaning beyond the schema's own incident_type enum explanation; baseline 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 names a concrete resource (the playbook) scoped to a specific input (an incident type) and enumerates exactly what the artifact contains: how it shows up, first hour, containment, eradication, recovery, evidence, aftercare. An agent immediately knows this returns complete IR guidance for one incident class. It stops short of differentiating itself from siblings such as najjab_overview or najjab_tabletop, which also return narrative content.

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?

Usage is only implied: 'the playbook for an incident type' signals you call it when you have an incident class and want end-to-end handling steps, which is adequate for a lookup tool. There is no explicit when-to-use/when-not-to-use statement and no mention of the alternatives in the sibling set, so an agent choosing between this, najjab_overview and najjab_tabletop gets no routing help.

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

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

Annotations cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), and the description adds the return shape: a scenario plus developments each tagged with a reveal minute, plus room questions. The word 'ready' also signals pre-authored rather than generated content. It stops short of stating pagination, size, or auth needs, so not a 5.

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?

A single front-loaded sentence with no filler; the core deliverable is stated first and the component list follows. Slightly dense but every clause earns its place.

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 carries the burden of describing the return value and does so adequately (scenario, timed developments, questions), which is what an agent needs to know before calling. The absence of any explicit sibling routing or size expectations keeps it from a 5.

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% and all three parameters carry enums with defaults, so the schema already documents lang, incident_type, and response_format. The description's 'for an incident type' restates the required parameter without adding format or constraint detail beyond the schema. Baseline 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 names a specific deliverable — a ready tabletop exercise for an incident type — and enumerates its components (scenario, timed developments, room questions). That is far more informative than a restated title and lets an agent distinguish it from najjab_playbook or najjab_draft_notice, though it never explicitly contrasts itself with those siblings.

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?

Usage is implied: reach for this when you need a pre-built exercise for a given incident type. However, no when-to-use condition, prerequisite, or named alternative (e.g. najjab_playbook) is given, so the agent must infer selection from the sibling list alone.

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