Assess repository contribution readiness before an agent begins work, preventing failed attempts and wasted time.
Assess repository contribution readiness before an agent starts work.
| Name | Required | Description | Default |
|---|---|---|---|
| repo_url | Yes | ||
| change_type | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.0Input schema / properties / access_tokenRemoved value: -{
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "title": "Access Token"
-}v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'assess,' which implies a read-only operation, but discloses nothing about network access, repository fetching, authentication requirements, failure modes, or side effects. An agent has little insight into what invoking this tool actually does.
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 a single, front-loaded sentence with no filler. It efficiently communicates the core purpose and the intended use timing. Every word earns its place.
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?
Despite having an output schema, the tool still lacks essential context for correct invocation: parameter semantics are absent, behavioral traits are undisclosed, and no guidance is given about prerequisites or limits. For a tool that likely fetches external repository data, the description is too thin to be considered complete.
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 0%, and the description adds no meaning to either parameter. 'repo_url' and 'change_type' remain unexplained, including what change_type values are valid or how they influence the assessment. The description fails to compensate for the schema's lack of documentation.
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 states a clear action and resource: 'Assess repository contribution readiness before an agent starts work.' This distinguishes it as a pre-work assessment tool, but it does not explicitly differentiate it from sibling tools like payment_preflight and bounty_reality_check, which are also preflight-style checks.
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 phrase 'before an agent starts work' provides clear timing/context for when the tool should be used. However, it gives no exclusions, alternatives, or guidance on when a different sibling tool would be more appropriate, so it stops short of full routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.