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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds 'No auth required,' which is genuinely useful behavioral context beyond the annotations. It also enumerates the returned structure (beats[], stories[], datespan, classification, published), giving the agent a concrete picture of the payload.

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 dense sentences, front-loaded with the core action and return shape, with no filler. The return-field enumeration is slightly run-on but every element earns its place since there is no output 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?

With no output schema, the description usefully enumerates the return tree and notes that no auth is needed, which covers the main things an agent needs to call and interpret this tool. It lacks any error behavior (e.g., unknown slug) or ordering context, keeping it short of 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% with a single required slug parameter already documented as coming from ic_signal_list_issues. The description only restates the parameter and adds an example value ('issue-05'), which is marginal value over the schema, so 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?

States a specific verb and resource ('Fetch one issue by slug') and the schema reference to ic_signal_list_issues implies the lookup workflow. It does not explicitly differentiate itself from sibling ic_signal_get_latest, which also returns a single issue, so an agent must infer the distinction from 'by slug'.

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 explicit when-to-use or when-not-to-use guidance and never names an alternative such as ic_signal_get_latest or ic_signal_search. The only routing hint is the schema note that the slug comes from ic_signal_list_issues, which is workflow inference rather than stated guidance.

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