get_current_issue

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

With no annotations, the description carries the behavioral burden. It signals a read-only fetch and explicitly documents the `issue: None` edge case when no current issue is set, which is valuable operational information beyond the 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?

Two concise sentences with no filler. The action and scope are front-loaded, and the edge-case return value earns its place as a separate sentence.

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 simple read tool, purpose and the None edge case are covered, but the optional `journal` parameter is left undocumented. Because there is no output schema, a bit more detail about expected output or parameter semantics would make it 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?

The single parameter `journal` has no explanation in the description, and schema description coverage is 0%. The title 'Journal' and default null provide only minimal clues; the description does not clarify whether an ID or name is expected, or what null means behaviorally.

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 uses a specific verb ('Fetch') and resource ('the journal's current issue'), and qualifies it as 'the one featured on the home page.' This clearly distinguishes it from sibling tools like get_issue or list_issues without needing to inspect their schemas.

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 home-page qualifier gives useful context for when the tool applies, but the description never names alternatives or states when to prefer get_issue/list_issues instead. Usage is implied rather than explicitly guided.

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