github_repos_set_status_check_contexts

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

With no annotations and a terse description, the tool's behavioral traits are entirely hidden. The description does not disclose that this operation likely replaces all existing contexts, requires specific permissions, or has any side effects.

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 under-specified; one short sentence provides no actionable information. Conciseness should not sacrifice clarity.

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?

Given no output schema, no annotations, and minimal parameter descriptions, the description is completely inadequate for an agent to understand what the tool does, when to use it, or what the expected outcome is.

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 description adds no meaning beyond the input schema. Parameter descriptions in the schema are minimal (e.g., 'owner', 'repo', 'branch', 'Request body (JSON object)'), and the description does not clarify the structure or purpose of the 'body' parameter.

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 'Set status check contexts' is a tautology that restates the tool name without providing a specific verb-resource relationship. It does not clarify what 'status check contexts' are or how this action differs from adding or removing contexts.

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 offers no guidance on when to use 'set' versus the sibling tools 'add_status_check_contexts' or 'remove_status_check_contexts'. No context about prerequisites or alternatives is provided.

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