github_repos_remove_status_check_contexts

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

With no annotations, the description bears full responsibility for behavioral details. It fails to disclose that this operation modifies branch protection settings, requires admin permissions, or what the implications are. The minimal description leaves the agent uninformed.

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 extremely short, which could be seen as concise, but it lacks necessary details to be effective. It is not well-structured beyond a single phrase.

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 a minimal description, the tool definition is incomplete. It misses information about prerequisites (e.g., branch protection must exist), side effects, and expected outcomes.

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 input schema descriptions are trivial (just parameter names), and the tool description adds no extra meaning. It does not explain what 'branch' refers to or that 'owner' and 'repo' are standard. With 100% schema coverage but low-quality descriptions, the tool description should have compensated but did not.

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 'Remove status check contexts' indicates the action but is vague: it does not clarify whether all contexts are removed or specific ones, and the input schema lacks a 'contexts' parameter. Among siblings like 'remove_status_check_protection' and 'add_status_check_contexts', the exact scope is ambiguous.

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 on when to use this tool versus alternatives such as 'set_status_check_contexts' or 'remove_status_check_protection'. The description provides no context about prerequisites or scenarios.

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