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

With no annotations, the description carries the full behavioral burden; it usefully discloses that the issue is attributed to Eco and that 'nothing in the code changes' (i.e., non-destructive, no repo mutation). It stops short of stating connection/permission requirements, idempotency, or what happens on repeated calls.

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 tightly written sentences with zero redundancy; the core action is front-loaded and the safety note follows. Every clause adds information (attribution, content types, non-mutation).

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 mutation tool with no annotations and no output schema, the description covers intent and the non-destructive nature well but omits what the call returns (issue number/URL), permission prerequisites, and behavior on duplicates. Adequate but with clear gaps.

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 three documented parameters (repo as owner/name, title, Markdown body), so the schema already carries the parameter semantics. The description adds no format or constraint detail beyond what the schema states, making the baseline 3 appropriate.

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 verb and resource ('Open an issue in a GitHub repository') and clarifies the intent ('a finding, a proposal or a to-do for the team'). It does not, however, explicitly distinguish itself from the sibling github_propose_change, which an agent might reasonably confuse with this tool.

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 through the enumerated content types (finding, proposal, to-do), which helps an agent decide what belongs in an issue. But there is no explicit when-to-use vs. when-not guidance and no mention of the github_propose_change alternative for code changes, leaving the choice to inference.

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