getRepoInfo

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states 'Get basic information', which implies a read-only operation but does not explicitly confirm this, nor does it mention potential errors, rate limits, or permissions. The lack of detail leaves significant ambiguity.

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 concise at one sentence, but it is under-specified and does not provide enough detail to be genuinely useful. It is not a verbose description, but it lacks substance, so the appropriate size is not matched with informative content.

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 tool with no output schema, the description should explain what information is returned, but 'basic information' is left undefined. It also lacks any context on error handling or return format. Given the simplicity of the tool, some completeness is expected, but the description falls short.

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 sole parameter 'repo' is a string with no description, and the tool description does not explain what format is expected (e.g., 'owner/repo' vs. URL). With 0% schema description coverage, the parameter semantics are entirely unexplained, making correct invocation difficult.

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 uses a specific verb 'Get' and identifies the resource as 'repository', clearly indicating it retrieves repository information. However, the phrase 'basic information' is vague and does not specify what fields are returned, nor does it explicitly distinguish this tool from siblings like listOpenIssues.

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 the sibling tools. The description is a single sentence with no context about use cases, prerequisites, or alternative tools, leaving the agent to infer when getRepoInfo is appropriate.

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