Create Issue Now

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only notes the dependency on a GitHub client but does not disclose side effects, required permissions, reversibility, or what happens on successful creation. For a mutation tool, this is a significant gap.

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?

The description is a single, front-loaded sentence that states both the purpose and a key prerequisite without extraneous words. It is concise, though it is also sparse and could include more useful detail without becoming verbose.

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?

An output schema exists, so return values are covered, but the description leaves open what a 'chain' is, how chain_id should be obtained, and what 'requires GitHub client' entails (e.g., authentication, availability, setup). For a create operation, it does not provide enough context for an agent to confidently invoke it without prior knowledge.

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 0%, so the description must compensate. The phrase 'for a chain' weakly maps chain_id to a chain identifier, but it does not explain how to obtain the chain_id, what constraints apply beyond type integer, or what a chain represents in this context. The semantic value added is minimal.

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 clearly states a specific verb-resource pair ('Create a GitHub issue') and scopes it to a chain, which distinguishes it from sibling tools like list_chains, get_chain, retry_now, pause_chain, resume_chain, set_config, and health. An agent can tell exactly what this tool does without opening the 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?

The description implies usage by stating what the tool does ('create a GitHub issue for a chain') and includes the prerequisite 'requires GitHub client.' However, it provides no explicit guidance on when to use this instead of siblings, nor any exclusion conditions or alternative recommendations.

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