git-asmt-repo

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

With no annotations, the description carries the burden of behavioral disclosure. It explains that the tool 'Owns the WHAT' and delegates HOW to L2 and course coordinates to L3, adding architectural context. However, it does not describe concrete invocation behavior, side effects, or return format beyond the existence of an output schema. This is a moderate disclosure.

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 dense but each sentence adds value: it defines the scope, the WHAT pipeline, delegation to L2/L3, and usage instructions. It is front-loaded with 'GLOBAL, language-agnostic L1 abstract.' No wasted words, though the chain 'audit → instruction-fidelity harness → prove 100/100 → ship the Starter → gates' is compact and may require interpretation.

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's abstract nature, no parameters, and presence of an output schema, the description sufficiently situates it within the broader system (L1 vs L2 vs L3, course wrappers). It does not explain what a caller should expect on invocation, but the output schema covers that. The description is complete enough for an agent to understand its place and usage.

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?

There are zero parameters and the schema coverage is 100% (vacuously), so the baseline is 4. The description does not need to add parameter details; it correctly focuses on the tool's role. No additional parameter semantics are required.

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 clearly identifies the tool as a global, language-agnostic abstract for building and testing GitHub coding-assignment repos, distinguishing it from siblings by making explicit its L1 role and delegation to L2/L3. It lacks a concrete verb+resource phrasing but communicates scope and intent effectively.

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?

The description provides explicit usage guidance: 'Use as the shared core every course's git build/test wrapper points to' and 'NEVER re-implement this per course.' It also names the alternatives (L2 language skills, L3 course wrapper), making it clear when to use this tool versus others.

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