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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it discloses what the call returns (enabled state and the last two, or all, duty periods) and cites the underlying GET /v3/duties/summary endpoint, which matters because 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?

A single tight sentence plus the endpoint, with the resource and payload front-loaded before the HTTP path. Slight jargon ('Duty assistant info') costs it a point but there is 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?

For a read-only, zero-required-param tool with full schema coverage and no output schema, the description covers scope, payload shape and endpoint adequately. Missing only the routing distinction against sibling duty tools and any note on result volume when last_two_only is false.

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 fully documented, and the baseline is 3. The phrase 'last two (or all) duty periods' does echo last_two_only and clarify what setting it false yields, but that is largely a restatement of the schema's own 'Only the last two duties (default true)'.

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 ('duty assistant info per team') and enumerates the payload — enabled flag plus last two (or all) duty periods — which lets an agent distinguish it from a bare status read. It stops short of naming the sibling it overlaps with (signl4_get_duty_status, signl4_list_duty_schedules), so differentiation requires 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?

The description gives no when-to-use guidance and never mentions the closely related signl4_get_duty_status or signl4_list_duty_schedules siblings. An agent must guess whether this summary or a status/schedule call is the right choice for a given question.

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