github_repos_add_status_check_contexts

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

The description does not disclose behavioral traits such as that this is a write operation modifying branch protection rules, any destructive consequences, or required permissions. Without annotations, the description provides no behavioral context beyond the name.

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 minimal and front-loaded, with no redundancy. However, conciseness should not come at the expense of informativeness; the single phrase lacks sufficient detail for a tool with a nested parameter.

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 the absence of annotations and the complexity of the 'body' parameter, the description is incomplete. It does not explain what status check contexts are, how to structure the body, or the tool's effect on branch protection. An output schema could help but is absent.

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?

While schema coverage is 100%, the parameter descriptions in the schema are tautological (e.g., 'owner' described as 'owner'). The tool description adds no additional meaning to the parameters, especially the opaque 'body' field. It fails to explain what the body should contain.

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 'Add status check contexts' clearly states the verb and resource, but it does not differentiate from sibling tools like 'set_status_check_contexts' or 'remove_status_check_contexts'. The lack of specificity on whether it appends or replaces could confuse agents.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., existing branch protection rules) or exclusions, leaving the agent without decision-making support.

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