get_repo_health

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

No annotations are present, so the description carries the full behavioral disclosure burden. It only says 'Get' and does not describe the return shape, data sources, required permissions, rate limits, or side effects. The read-only nature is implied but never stated.

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 one short sentence with no filler, and the core verb and resource are front-loaded. It is appropriately sized, though the brevity sacrifices useful differentiation from sibling tools.

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 two-parameter read tool the basics are present, but the lack of an output schema and the undefined term 'health information' leave a significant gap. An agent cannot reliably predict what the tool returns or when to choose it over get_health_score.

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 already describes both parameters (owner and repo) with 100% coverage, so the parameter baseline is 3. The description adds no meaning beyond the schema's property descriptions.

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 states a specific verb ('Get') and resource ('health information for a GitHub repository'). However, 'health information' is not defined, and the description does not differentiate this from the sibling get_health_score, so it is clear but lacks sibling distinction.

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?

There is no guidance on when to use this tool versus get_health_score, check_ci_status, analyze_dependencies, or analyze_code_scanning. No usage context, exclusions, or alternative routing is provided; the agent must infer from the tool name alone.

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