github_check_repo_settings

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

No annotations are provided, so the description must fully disclose behavioral traits. It indicates a read-only check by convention but does not explicitly state it is non-destructive, mention authentication requirements, rate limits, or any side effects. The description lacks sufficient detail for safe invocation.

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, concise sentence covering the tool's purpose and key details. It is front-loaded with the action and specifics. However, it could be slightly more structured (e.g., listing parameters or noting read-only) without adding length.

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 simple tool with only two parameters and no output schema, the description adequately covers the checks performed and the related policy IDs. It gives enough context for an agent to understand what the tool does without needing additional information.

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 coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema's parameter names and descriptions (owner and repo). It does not clarify format, validation constraints, or usage context for the parameters.

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 it checks repository security settings and lists three specific areas (SECURITY.md, private vulnerability reporting, fork restrictions) along with policy IDs. This verb-resource combination is specific and distinguishes it from sibling tools that focus on other aspects like branch protection or code scanning.

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 for security settings checks but does not provide explicit guidance on when to use this tool versus alternatives. There is no mention of when not to use it or which sibling tools cover overlapping areas.

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