github_default_repo

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

No annotations are provided, so the description must disclose behavior. It mentions routing/auth details but does not describe the core operation's side effects, whether it is read-only, or what the tool actually does. The behavioral characteristics are unclear.

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 short but includes unnecessary routing details that do not help the agent. It is not front-loaded with the core purpose. While concise in length, it sacrifices clarity for brevity.

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 tool has an output schema and many sibling tools, the description is incomplete. It does not explain what the tool returns, how to interpret the output, or how it differs from similar GitHub tools. The agent lacks crucial context to use it correctly.

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 schema has 0% description coverage. The description only repeats the parameter name 'arguments' and says it is a JSON string for the connector operation. It adds no meaning about the expected structure, keys, or examples, leaving the agent to guess.

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 only states 'Github connector operation `default_repo`' without explaining what the operation does. It does not specify whether it retrieves, sets, or lists a default repository. The mention of routing and authentication details does not clarify the purpose.

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. With sibling tools like github_default_org, github_default_pr_base_branch, and many others, there is no differentiation or scenario-based advice.

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