github_repos_get_community_profile_metrics

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

No annotations are present, so the description must carry the full burden of behavioral transparency. The description only states it 'gets' metrics, implying a read operation, but does not disclose any behavioral traits such as authentication requirements, rate limits, or the nature of the metrics. It fails to provide sufficient transparency.

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 very concise, consisting of a single phrase. It is front-loaded and efficient, but it could benefit from a bit more detail without becoming verbose. While it is not wasteful, it is slightly underspecified.

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 minimal description, no output schema, and no annotations, the tool is contextually incomplete. An agent would lack understanding of what the community profile metrics include, expected return values, and how to handle the response. The description covers only the basic purpose.

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?

Input schema coverage is 100%, but the parameter descriptions are minimal ('owner', 'repo') and add no value beyond the names. The tool description does not clarify parameter semantics or expected formats. The baseline score is 3 because the schema covers the parameters, but no additional meaning is added.

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 'Get community profile metrics' clearly indicates the action (get) and the resource (community profile metrics). The tool name also reinforces this. However, it does not specify what these metrics include, leaving some ambiguity about the exact data returned.

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 usage guidelines are provided. There is no mention of when to use this tool versus alternatives, prerequisites, or context. The agent receives no help in deciding to invoke this tool.

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