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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered, but the description adds real context beyond them: 'No auth required' and the guarantee that output matches an element of ic_signal_list_issues.issues[]. It does not describe error/empty states or pagination, but for a read-only summary tool this is solid.

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?

Front-loads the core purpose and keeps everything in a compact couple of sentences. The inline 'Args:' block partially duplicates the schema's own description, which is slight redundancy, but nothing is padded.

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?

No output schema exists, but the description compensates by defining the return shape by reference (same as an element of ic_signal_list_issues.issues[], or stories[] when inlined). Auth requirement is disclosed. Minor gap: no mention of behavior when no issues exist.

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%, so baseline is 3, but the description genuinely adds meaning: include_stories=true inlines stories[] with id/title/dek and is justified as avoiding a follow-up call. This explains the *why* and the exact content beyond the schema's terse 'true inlines the issue's stories'.

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 ('returns the most-recent issue summary') and pins down the exact return shape by equating it to 'one element of ic_signal_list_issues.issues[]'. It also names two siblings (ic_signal_list_issues and ic_signal_get_issue), so an agent can distinguish it without opening a schema.

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?

Frames itself as a 'convenience tool' for grabbing the latest issue and explicitly notes that include_stories=true saves a follow-up ic_signal_get_issue round trip, which gives clear routing context. It stops short of an explicit when-not statement (e.g., when to prefer ic_signal_list_issues or ic_signal_search instead).

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