Get Repository

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the useful behavioral note that this is intended as a frequent, cheap verification call, but says nothing about authentication requirements, rate limits, or failure behavior for nonexistent repos.

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?

Two compact sentences with the returned payload front-loaded before the usage note. The phrase "Eager daily driver tool" is mildly promotional filler, but the rest is dense and earns its space.

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?

With no output schema, the description carries the burden of describing return values and does so by enumerating the metadata fields. For a two-parameter, fully-annotated read tool this is essentially complete; only the error behavior for a missing repo is unaddressed.

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 description coverage is 100% — both owner and repo are documented with concrete examples in the schema itself. The description only restates "for an owner/repo" and adds no format, casing, or validation detail beyond what the schema provides, so the baseline of 3 applies.

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 gives a specific verb (get) and resource (repository) and enumerates the returned fields — metadata, visibility, description, default branch, clone URLs, star count, topics — so the agent knows exactly what comes back. It does not explicitly contrast itself with siblings like get_file_contents or get_commit, but the resource is distinct enough that confusion is unlikely.

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?

"Eager daily driver tool for verifying repository configuration and existence" implies the usage context (existence/configuration checks) but names no alternatives and states no when-not conditions. Usage is implied rather than prescribed, which is the definition of a 3.

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