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

With no annotations provided, the description carries the burden of disclosure. It does reveal a key non-obvious behavior: the operation 'republishes full announcement' rather than simply updating a tag. However, it does not describe other important implications, such as whether the maintainer list is additive or replaced, potential side effects, or required authentication beyond what the schema mentions.

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 one concise sentence with a parenthetical that packs important mechanism details. It is front-loaded with the primary action and avoids unnecessary words, though the parenthetical makes it slightly dense.

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?

This is a mutation tool with no annotations, no output schema, and limited description. It explains the republishing mechanism but not the full effect on the announcement, whether it is destructive, what the expected outcome is, or any prerequisites. The reference to 'matches gittr UI' may be unhelpful to users unfamiliar with that UI, leaving the description incomplete for a tool with this complexity.

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 description coverage is 60% (three of five parameters have descriptions), and the tool description does not clarify the remaining parameters (relays, repoId) or add meaning to the existing ones. While 'maintainer' hints at collaboratorPubkey, the description fails to compensate for the uncovered parameters, so it adds little semantic value beyond the schema.

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 states the action ('Add maintainer') and the specific resource ('kind 30617'), and it distinguishes the tool from sibling tools by detailing the underlying mechanism ('republishes full announcement with updated maintainers tag'). The reference to 'matches gittr UI' adds further specificity, making the purpose unambiguous.

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 implies usage when one wants to add a maintainer, but it does not explicitly state when to use this tool over alternatives or provide exclusions. The mention of matching the gittr UI provides some context but no direct guidance on alternatives or when not to use it.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it delivers meaningful traits: 'Auto-loads .nostr-keys.json if privkey omitted' covers auth needs, and 'pinToBlossom streams files to primal/ditto/haven (never blossom.gittr.space)' discloses destination behavior including an explicit exclusion. It does not cover failure modes or side effects on existing announcements, but the key behavioral traits are surfaced.

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?

Three dense sentences with zero filler: the core purpose is front-loaded in sentence one, usage analogies and the tagless constraint in sentence two, and optional behaviors (pinToBlossom, key auto-load) in sentence three. Every sentence earns its place and the most critical routing information appears first.

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 complex 15-parameter tool with no output schema and no annotations, the description covers purpose, usage context, constraints, auth behavior, and pin destinations, and the 93% schema coverage fills in defaults and failure semantics (e.g., 'Pin failure still announces the forge URL'). It falls short only in not describing the expected return value/output and not explicitly naming the sibling tool for the tagless case.

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 high at 93%, so the baseline of 3 applies and the schema already documents most parameters. The description adds some contextual value beyond the schema—'pinToBlossom streams files to primal/ditto/haven (never blossom.gittr.space)' clarifies semantics and privkey auto-loading behavior is reinforced—but this is incremental rather than substantial.

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 specific verb and resource: 'Announce software to Zapstore/NIP-82 (kinds 32267/30063/3063) from a forge Release binary.' It distinguishes itself from related tools by declaring 'Never a tagless app' and referencing gittr UI equivalents, so an agent can separate it from publishSoftwareAnnounce and publishRepoAnnouncement without inspecting the schema.

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 gives clear context for when to use the tool: 'Same as gittr Nostr Apps (latest tag) or Releases → Announce on Nostr (tag=)' and explicitly states the when-not condition 'Never a tagless app.' However, it points to UI analogues rather than naming sibling tools (e.g., publishSoftwareAnnounce) as the alternative for tagless cases, so the exclusion routing is slightly indirect.

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

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

With no annotations, the description carries the burden itself and does reveal meaningful behavior: it scans manifests, performs an external POST to OSV, and bypasses the audit UI flag. However, it does not state whether the operation is read-only, what authentication or permissions are required, or what the response contains.

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?

Three short sentences deliver the action, target, endpoint, UI parity, and a prerequisite edge case with no filler. The core scanning/audit behavior is front-loaded before secondary orientation.

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?

The tool is moderately complex with four optional-looking parameters and no output schema or annotations. The description gives a clear purpose but omits repoId/ownerPubkey semantics and any return or side-effect expectations, so an agent would need to infer important invocation details.

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 coverage is only 50%: branch and packages have descriptions, while repoId and ownerPubkey do not. The description does not compensate for the undocumented identifiers, leaving the key repo reference and possible auth parameter under-specified.

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?

Description uses a specific verb ('Scan') with a concrete resource ('gittr bridge repo’s manifests'), lists example manifest files, and names the exact OSV endpoint. It also anchors the tool's role to the Dependencies tab, giving an agent enough to distinguish it from the many repo/file sibling tools.

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 'Same data as the gittr Dependencies tab' line supplies clear context for when this tool is relevant, and 'Does not require the website audit UI flag' removes a likely prerequisite. It doesn't explicitly name an alternative or a when-not-to-use case, but no sibling appears to provide the same audit capability.

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

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 mentions that it is a POST request, implying a mutation, but says nothing about side effects, authorization requirements, reversibility, or what happens on success/failure. This is a significant gap for a tool handling funds.

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 extremely short and under-specified. While it is not verbose, it sacrifices necessary details for brevity, making it an under-specified snippet rather than a useful, front-loaded explanation.

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 complexity (9 parameters, no output schema, no annotations), the description is completely inadequate. It does not explain the tool's purpose, parameters, behavior, or return value, leaving the agent with almost no contextual understanding.

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 9 parameters with 0% description coverage, and the description provides no parameter information. It mentions 'recipient' generically but does not explain any of the fields like lnurl, bridgeUrl, issueRepo, or how they relate to the action. The description fails to compensate for the schema's lack of semantics.

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 'claim withdraw to recipient' is vague and unclear. It does not convey the exact action: is it claiming a withdrawal or withdrawing a claim? The endpoint path adds some context, but the purpose remains ambiguous and does not distinguish it from sibling tools like bountyCreateWithdraw.

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?

There is no guidance on when to use this tool versus alternatives. It simply states the endpoint and action, with no context about prerequisites, related tools, or appropriate scenarios. This leaves the agent without guidance on selection.

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

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

With no annotations, the description must disclose effects. It only states the endpoint and protocol; it does not explain side effects, auth requirements (despite lnbitsAdminKey/InvoiceKey in schema), or what happens when invoked.

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 extremely brief, but it under-specifies rather than being efficiently concise. It provides a bare endpoint reference without meaningful elaboration, so it feels incomplete rather than crisp.

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?

The tool has 7 parameters, no output schema, no annotations, and no parameter descriptions. The one-line descriptor cannot adequately convey the operation, making it insufficient for correct invocation.

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?

All 7 parameters are undocumented; the description does not clarify the meaning of amount, issueId, or the various URLs/keys. The schema provides only names and required status, 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 identifies the HTTP endpoint and the LNURL-withdraw mechanism, clearly indicating this tool creates a withdrawal for a bounty process. It has a specific verb (create-withdraw) and resource (bounty flow), but does not explicitly differentiate from sibling tools like bountyClaimWithdraw.

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 about when to use this tool versus alternatives such as bountyClaimWithdraw or createBountyInvoice. There are no conditions, prerequisites, or exclusions stated.

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

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

No annotations are provided, so the description must disclose behavioral traits. It only states that it pays a bounty, but does not mention that this is an irreversible financial transaction, requires admin keys (lnbitsAdminKey), or any side effects. The schema includes sensitive parameters but the description does not address them.

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, concise sentence with the HTTP method and endpoint, making it front-loaded and efficient. However, it is slightly cryptic with the dash separation, though it 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?

For a tool with 8 parameters, no annotations, and no output schema, this description is severely incomplete. It fails to explain the required parameters (bountyId, recipientPubkey, bountyAmount), the role of bridgeUrl/lnbitsUrl, or the implications of releasing a bounty.

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 does not explain any of the 8 parameters. The phrase 'recipient Lightning address' vaguely references recipientLnurl or recipientLud16, but no parameter names, types, or usage details are provided.

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 states the action 'pay bounty to recipient Lightning address' with an explicit endpoint 'POST /api/bounty/release'. It distinguishes itself from siblings like submitBounty and bountyClaimWithdraw by indicating this is the release/payment step.

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 no guidance on when to use this tool versus alternatives like submitBounty or bountyClaimWithdraw. It simply states the function without context, prerequisites, or exclusions.

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

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

With no annotations, the description carries the full burden of disclosure. It only states the endpoint and function, omitting any mention of read-only semantics, response format, permissions, or side effects. Since GET implies a read, but this isn't explicitly stated, the agent is left without critical behavioral context.

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 sentence and easy to read, with no wasted words. However, it's so brief that it lacks necessary detail, making it more under-specified than appropriately concise. It earns a middle score for being clear but not overflowing.

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 complexity of 5 parameters, no annotations, and no output schema, this description is far from complete. It doesn't explain parameter roles, return values, or usage scenarios, so an agent cannot reliably invoke the tool correctly without external knowledge.

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 doesn't mention any parameters. All 5 parameters (path, repo, branch, bridgeUrl, ownerPubkey) are undocumented, leaving the agent without guidance on required combinations, defaults, or formats. The description completely fails to compensate for the missing schema descriptions.

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 action (GET), the resource (file-content), and the context (from bridge), making it distinguishable from other file-related tools like getFile. However, it doesn't explicitly contrast with sibling tools or explain what 'bridge' means, so it's not a full 5.

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 like getFile or bridgeListFiles. The description is purely declarative and offers no contextual cues or exclusions.

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

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

No annotations are provided, and the description does not disclose behavioral aspects such as read-only semantics (GET is implied but not stated), authentication requirements, rate limits, or return format. The description carries the full burden and fails to address any behavioral traits.

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 URL string, which is extremely short. However, this is under-specification rather than conciseness: it omits necessary explanatory content. A helpful description would be a few sentences explaining the tool's purpose and parameters.

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?

The tool has two required parameters, three optional, no output schema, and no annotations. The description provides no contextual information about behavior, response, or use cases. This is completely inadequate for an agent to select and invoke the tool 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?

Schema description coverage is 0%, and the description does not explain any of the five parameters (repo, limit, branch, bridgeUrl, ownerPubkey). The schema itself provides no parameter descriptions, so the tool is effectively unusable without external knowledge.

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 is only 'GET /api/nostr/repo/commits', which is an HTTP endpoint path rather than a clear statement of functionality. While the HTTP method and resource hint at listing commits, it lacks explicit action wording or a resource description that distinguishes it from siblings like getCommitHistory or bridgeListRefs.

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?

There is no guidance on when to use this tool versus alternatives such as getCommitHistory or bridgeListRefs. The description provides no context, prerequisites, or exclusions.

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

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

With no annotations, the description carries full burden for behavioral disclosure. It implicitly indicates a read-only GET request, but does not mention edge cases, auth requirements, rate limits, or response format, leaving significant behavioral 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 a single clean sentence with no wasted words. However, it is quite terse and under-specified, which slightly reduces its effectiveness despite being concise.

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 five parameters, no output schema, and no annotations, the description is far from complete. It only states the core action without explaining required context, the role of bridgeUrl, or how results are returned.

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 coverage is 0%, and the description only hints at the 'branch' parameter. Other parameters such as ownerPubkey, repo, bridgeUrl, and includeSizes are left unexplained, adding minimal value over the bare schema.

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 states the action and resource: 'GET /api/nostr/repo/files — list files for branch'. It specifies the HTTP method and endpoint, distinguishing it from sibling tools like getFile, bridgeListRefs, and bridgeListCommits.

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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites.

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

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

The description carries no behavioral information beyond the HTTP method. It does not disclose side effects, return behavior, or any operational context. With no annotations available, the description completely fails to inform the agent about what happens when this tool is invoked.

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 extremely short, but this is under-specification rather than conciseness. It consists of a single endpoint string and does not earn its place by adding value. It is not a meaningful description.

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, no annotations, and a 0% parameter coverage, the description is completely inadequate. The tool has moderate complexity with three parameters, but the description offers zero context, making it impossible for an agent to use the tool 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?

Schema description coverage is 0%, and the description provides no explanation of the three parameters (repo, bridgeUrl, ownerPubkey). The agent is left without any semantic clues about what each parameter means or how to use them.

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 is just 'GET /api/nostr/repo/refs', which is an HTTP endpoint rather than an explanation of what the tool does. It restates the resource 'refs' without providing a verb or action, and does not clarify what listing refs means. This is close to a tautology, offering no insight into the tool's actual 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?

There is no guidance on when to use this tool versus alternatives. Sibling tools like bridgeListFiles and bridgeGetFileContent exist, but the description does not differentiate this tool or suggest any context for using it.

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

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

No annotations are provided, so the description carries the full burden. It only says 'check if repo exists' without disclosing the return format (e.g., boolean, HTTP status), error behavior, or whether it performs a network call to the bridge. No side effects or failure modes are mentioned.

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 concise sentence that directly states the purpose. It is not overly verbose, but it lacks necessary details; however, for conciseness alone it earns a decent score.

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 annotations, no output schema, and no parameter explanations, the description is incomplete for safe invocation. An agent cannot predict the outcome or interpret a response. The tool complexity is low, but the description still fails to provide essential context beyond the purpose.

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 input schema has 3 parameters with 0% description coverage. The description does not explain what 'ownerPubkey', 'repo', or 'bridgeUrl' mean, nor how they are used in the existence check. The agent must guess their semantics.

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 the exact HTTP endpoint ('GET /api/nostr/repo/exists') and the operation ('check if repo exists on bridge'), making it clear this is a boolean existence check distinct from sibling tools like getRepo or listRepos.

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, no prerequisites, and no mention of whether it should be called before other operations. The agent is left to infer usage context.

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

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

With no annotations, the description must disclose safety and side effects. It indicates a write operation ('publish status') but doesn't mention whether it overwrites existing status, permission requirements, relay propagation, or preconditions like the issue being open. The '1632' status is unexplained.

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 concise sentence, but it is under-specified. 'Convenience' adds a little context, but the sentence doesn't effectively front-load actionable information. It is short without being informative.

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?

As a mutation tool with 6 parameters and no annotations or output schema, the description fails to cover required context like side effects, security requirements (privkey), or relationship to sibling tools. It provides only a minimal hint, making it inadequate for reliable agent use.

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 offers no parameter explanations. Required params (issueId, ownerPubkey, repoId, privkey) and optional ones (relays, content) are left entirely to the schema, which the agent must already know. The description adds no meaning beyond implying 'issue'.

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 specific action: publishing status 1632 (closed) for an issue, which effectively means closing an issue. It is clear and distinguishes from siblings like reopenIssue by the 'closed' status, though the numeric code '1632' is somewhat cryptic.

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 given on when to use this tool versus alternatives. The word 'Convenience' hints it is a wrapper, but it doesn't explain when to prefer closeIssue over lower-level publishStatusForRoot or how it contrasts with reopenIssue.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the HTTP method (POST), authentication requirements (lnbits credentials), and the post-payment action of publishing to Nostr. However, it does not disclose side effects on the bounty, whether the operation is idempotent, or what happens on failure. The description adds useful context but lacks important behavioral details.

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, two sentences long, and front-loaded with the main action. Every sentence adds valuable information: the endpoint, credentials, and the follow-up Nostr publication. There is no fluff or repetition.

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?

The tool has moderate complexity with a payment flow and a Nostr publishing step, and there is no output schema. The description covers the main action and the post-pay step, but it does not explain the expected return value (e.g., invoice details, payment request), how payment status is checked, or error scenarios. For an agent to use this tool effectively and handle the follow-up, more context would be beneficial.

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%, so the description must compensate. It explains the optional credential parameters (lnbitsUrl, lnbitsAdminKey) and mentions env var alternatives, but it does not explain the required parameters (issueId, amount) or what values they should take (e.g., amount in satoshis). The description gives only partial parameter guidance, leaving the most critical inputs ambiguous.

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 states the tool creates a Lightning invoice for bounty escrow, giving a specific verb and resource. It also provides the endpoint (POST /api/bounty/create), which precisely defines the operation. This distinguishes it from sibling bounty tools like bountyRelease or submitBounty.

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 clear context for when to use this tool (to create a Lightning invoice for bounty escrow) and gives instructions on authentication via env vars or passing credentials. It also mentions a follow-up action (publish via publishBountyToNostr after payment), which helps the agent understand the workflow. However, it does not explicitly mention when not to use it or compare with alternative tools.

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

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does disclose that signing is required and implies a write operation, but it does not explain the signing mechanism, side effects, or permission requirements beyond that.

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 sentence that front-loads the action and flags a critical requirement. There is no filler or redundant wording; 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?

With seven parameters, no annotations, no output schema, and no parameter descriptions, one sentence is insufficient. The description omits return value expectations, signing details, and how this tool relates to other issue/PR operations in the same domain.

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 parameter-level detail. 'REQUIRES signing' hints at the privkey parameter, but otherwise required fields like ownerPubkey, repoId, and relays are left entirely to their self-evident names.

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 and direct object ('Create an issue'), which clearly identifies the action and resource. It is distinct from related sibling tools like listIssues, closeIssue, and reopenIssue.

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 includes a prerequisite ('REQUIRES signing') but provides no explicit guidance on when to use this tool versus alternatives such as createPR or listIssues. Usage context is mostly implied by the tool name and sibling set.

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

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

With no annotations, the description carries the behavioral burden. It discloses the event kind (NIP-22, kind 1111), that replyTo creates a threaded reply, and that bounty events are unaffected. It does not mention signing/broadcasting to relays or output behavior, but the core publish semantics are clear.

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 sentences with no filler. The primary action is front-loaded, threading behavior is stated, and the important exclusion of bounty events is included compactly.

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 publishing tool with no annotations and no output schema, the description covers the core behavior, target, threading, and a likely point of confusion (bounty events). Minor gaps remain around relay usage, default behavior when relays are omitted, and what the tool returns, but these are not fatal for correct invocation.

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 coverage is 71% and the schema already documents most parameters including issueId, repoId, ownerPubkey, privkey, and replyTo. The description adds useful context for replyTo and the non-bounty exclusion, but it does not compensate for the undocumented relays and content parameters, which are left to inference.

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 specific verb ('Publish'), a specific resource ('NIP-22 comment (kind 1111) on an issue'), and clarifies it does not create or modify bounty events. This clearly distinguishes it from siblings like createPRComment, listIssueComments, and the bounty-focused tools.

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 makes the target context clear ('on an issue') and explicitly excludes bounty event creation/modification. It does not explicitly name alternatives such as createPRComment for pull request comments, but the issue scoping and event kind provide enough routing context for most calls.

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

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

With no annotations, the description carries the full burden. It discloses the signing requirement, which is useful, but fails to mention mutating side effects, authorization beyond signing, or the impact of creating the PR. This is a significant gap for a write operation.

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 exceptionally concise and front-loaded, with no filler. However, it is arguably too terse for a complex tool, though the conciseness itself is well-executed.

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 high complexity (10 parameters, no annotations, no output schema), the description is grossly incomplete. It does not explain the PR creation workflow, the meaning of signing, or how this tool relates to the CLI variant, leaving the agent under-informed for correct invocation.

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% across 10 parameters, and the description adds no parameter semantics. Beyond the parameter names (e.g., ownerPubkey, repoId, commitId), the description does not explain their roles or relationships, leaving the agent without essential input details.

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 the specific action and resource: "Create a pull request." This clearly differentiates it from siblings like createIssue (issues) and updatePullRequest (updates), which are distinct operations.

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 no guidance on when to use this tool versus alternatives such as createPRViaGittrCLI or updatePullRequest. The only extra hint, "REQUIRES signing," is a prerequisite rather than a usage guideline, and there are no exclusions or alternative tool mentions.

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

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

With no annotations, the description carries the full burden. It discloses that the tool publishes a NIP-22 comment, which implies a broadcast/write operation, but it does not mention signing requirements, relay usage, irreversibility, or any side effects beyond publishing.

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 is concise, though its brevity contributes to the lack of behavioral and contextual detail.

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 7 parameters, no output schema, and no annotations, this description is incomplete. It does not explain return behavior, relay or key handling, or the roles of several parameters, leaving an agent under-equipped to invoke 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?

Schema description coverage is only 43%, and the description only adds meaning around replyTo. Parameters like relays, repoId, content, and ownerPubkey remain undocumented in both the schema and description, so the description does not compensate for the coverage gap.

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 states a specific action—'Publish a NIP-22 comment (kind 1111) on a pull request'—and mentions the optional replyTo behavior. This distinguishes it from related tools like createIssueComment and listPRComments.

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 gives useful context: use it for pull request comments and optionally for threaded replies. However, it does not explicitly mention when to prefer this over alternatives such as createIssueComment, nor does it state any exclusions or conditions.

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

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

No annotations are provided, so the description carries the burden of disclosing behavioral traits. It explicitly mentions 'full flow including git push', which is a key mutating behavior beyond just creating a PR. However, it does not disclose potential side effects, auth requirements, failure modes, or reversibility, leaving transparency incomplete.

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 that captures the essential purpose and key behavioral detail (full flow with git push). Every word adds value, with no redundancy or filler.

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 6 parameters, no output schema, and no annotations, the description is too sparse. It fails to mention what the tool returns (e.g., PR URL), what the 'full flow' entails in detail, prerequisites like credentials, or how it handles errors. The recommendation is helpful but does not compensate for the missing operational context.

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 input schema covers 100% of the parameters, each with descriptions, so the baseline is 3. The tool description adds no additional parameter semantics beyond the schema, as it only mentions the CLI and push flow but does not explain parameters like privkey, repo, or branches.

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 states the tool creates a pull request via the gittr CLI and includes the full flow with git push, distinguishing it from the sibling createPR tool. The use of 'RECOMMENDED' adds a preference but does not explicitly name the alternative, so it falls short of a 5.

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 an explicit recommendation ('RECOMMENDED for PRs') and indicates the full flow includes git push, which implies this tool is the preferred choice for PR creation. However, it does not explicitly state when not to use it or name specific alternatives, so it lacks exclusivity guidance.

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

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

No annotations are provided, so the description carries full responsibility. It discloses that owner wallet keys are passed in the body, but does not state side effects, authentication requirements, rate limits, or whether the intent is immediately redeemable. The mutating nature is only implied by 'create'.

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 compact line, which is efficient, but it is more of an API endpoint label than a structured explanation. It contains no sentences and lacks logical breakdown of purpose, usage, and parameters.

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 8 parameters, no output schema, and no annotations, this description is severely under-specified. It provides no information about the request/response flow, prerequisites, or return value, making it inadequate for an agent to invoke 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?

Only 1 of 8 parameters has schema documentation (13% coverage). The description adds a vague reference to 'owner wallet keys in body', which hints at the owner* parameters, but does not explain repo, bridgeUrl, payerPubkey, or the LNBits/Blink parameters. It fails to compensate for the low schema coverage.

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 identifies the action as creating an invoice/payment intent for pay-to-push, which is a specific verb+resource. It distinguishes itself from sibling tools like pushToBridge and bounty invoice tools. However, the phrasing is cryptic, relying on HTTP jargon ('POST') and the action name 'create_intent' instead of a plain-language verb.

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 explicit usage guidance or alternative tools are mentioned. The phrase 'invoice for pay-to-push' implies the tool is used when a push requires payment, but there is no context on when not to use it or how it relates to sibling tools like getPushPaywallStatus or syncRepoPushPolicy.

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

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

No annotations are provided, and the description reveals no behavioral details: no side effects, permissions, mutability, output, or even a positive statement of what the operation performs. The only behavioral signal is a negative support restriction, which is insufficient for an agent to call this tool safely.

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 text is short and front-loaded with the limitation, but it is incomplete rather than appropriately concise. Every sentence earns its place for routing, yet no sentence addresses the tool's actual purpose.

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?

This is a 7-parameter tool with 3 required fields, no annotations, and no output schema, but the description only redirects users away from it. An agent cannot determine what createRelease does, what inputs mean in context, or what happens when it is invoked, so the definition is far from 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 86%, so most parameters already carry their own descriptions. The description adds no additional meaning to parameters like targetCommit, releaseNotes, or relays, earning the baseline score.

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 never states what createRelease actually does. It only says it is 'Not supported for UI release notes' and redirects to sibling tools, so the agent is left guessing whether this creates a release, a git tag, or something else.

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?

It provides explicit alternatives for two specific cases: 'announceSoftwareFromForgeRelease' for Zapstore/NIP-82 announce and 'listReleases + publishRepoState' for git tags. However, it never says when to use createRelease itself, so the positive usage condition is missing.

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

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

With no annotations provided, the description carries the burden. It discloses that credentials are auto-loaded from .nostr-keys.json and that the tool performs both file pushing and Nostr publishing. However, it omits return value behavior, error handling, and idempotency details.

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 and front-loaded with the primary action and benefit. The phrase 'Best for agents!' is slightly promotional but does not detract significantly. Each clause contributes to understanding the tool's purpose.

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 complexity (10 parameters) and lack of output schema, the description gives a clear high-level overview but does not explain what the tool returns or how it handles potential failures. It relies on schema descriptions for parameter details, which is acceptable but leaves gaps for an agent.

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 already covers most parameters with descriptions (90% coverage). The description adds minimal parameter-specific insight beyond noting auto-loading of credentials, which relates to the privkey parameter. It does not compensate for the small coverage gap or explain parameter interactions.

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 'CREATE A REPO' and clearly states the scope: pushing files and publishing to Nostr. It distinguishes itself from sibling tools like createIssue or pushToBridge by combining operations into one call.

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 implies the primary use case: creating a repo with files in one call, and notes it's 'Best for agents!' It does not explicitly name alternative tools or state when not to use it, but the context of a one-call combined operation is clear.

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

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions 'soft-delete' (non-destructive) and 'owner only' (permission), but does not explain what soft-delete means in practice (e.g., recoverability), any side effects, or what happens to the repository. This is a significant gap for a mutating tool with zero annotation support.

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 sentence that front-loads the alias relationship and the action. There is no wasted wording, and the structure is direct. However, it is extremely brief, which compromises completeness, but for pure conciseness it earns a high score.

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 5 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain return values, parameter usage, or the practical implications of 'soft-delete'. The reliance on an alias to softDeleteRepo does not stand alone, as no details from that tool are provided here.

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 provides no parameter details. There are 5 parameters (name, relays, repoId, privkey, description) but the description does not explain their roles or how to use them. The 'owner only' hint is too vague to compensate for the complete lack of parameter semantics.

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 states the action ('soft-delete'), the resource (a NIP-34 repository), and the access restriction ('owner only'). It also distinguishes itself from the sibling softDeleteRepo by explicitly noting it is an alias, making the tool's purpose unambiguous.

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 'Alias for softDeleteRepo' implies the tool is used interchangeably with softDeleteRepo, which is a form of usage guidance. The 'owner only' note adds a prerequisite. However, it does not explicitly state when to choose this over other deletion alternatives or when not to use it, leaving the guidance somewhat implicit.

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

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

With no annotations, the description carries the full burden. It discloses the NIP-09 kind 5 mechanism and the non-deletion of the git repo, but omits behavioral details like auth requirements (privkey/ownerPubkey), whether deletion events are broadcast to relays, irreversibility, and ownership verification. Partial but not complete transparency.

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. Every phrase adds value: protocol, action, resource type, and an important exclusion.

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 deletion tool with 4 parameters, no output schema, and no annotations, the description is relatively thin. It does not explain return values, error conditions, relay usage, or whether ownership is required. It provides the core function but lacks operational context an agent would need for correct invocation.

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 coverage is 50% (only eventIds and privkey have descriptions). The description adds useful context that eventIds refer to NIP-82 app/release/asset events, but relays, privkey, and ownerPubkey are not elaborated on beyond the schema. It partially compensates for the gaps.

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 states the tool performs NIP-09 kind 5 deletion for previously published NIP-82 event IDs, specifying the resource types (app/release/asset) and explicitly noting it does not delete the git repo. This distinguishes it from sibling publish/announcement tools and repo deletion operations.

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 implies the use case for removing previously published NIP-82 announcements and explicitly excludes git repo deletion, which provides a clear boundary. However, it does not explicitly name alternative tools or conditions where this tool should not be used.

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

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 adds useful safety context ('never returns private key', 'hex/npub only'), but does not mention output shape, possible errors, or side effects. This is adequate for a simple status check but not comprehensive.

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 two short sentences, front-loaded with the core purpose and followed by essential usage and safety notes. Every word earns its place with no redundancy.

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 zero-parameter, simple status tool, the description provides purpose, format, security, and usage ordering. However, with no output schema, it doesn't explicitly state whether the tool returns a boolean, string, or object, nor what happens if keys are not loaded. The implicit 'whether' covers this partially, but a small gap remains.

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 tool has 0 parameters, so the baseline is 4 per the rubric. Schema coverage is 100% (empty schema), and the description adds no param-specific detail, which is appropriate given there are no parameters to explain.

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 'Show' and names the resource 'Nostr keys', with explicit scope 'whether keys are loaded'. It also distinguishes itself from sibling tools by specifying the hex/npub format and the 'never returns private key' safety qualifier, making its purpose unambiguous.

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?

Explicitly instructs to 'Use first in a session', giving clear timing/order context. It does not explicitly name alternatives or exclusions, but the session-first guidance effectively differentiates it from tools like loadCredentials or getPublicKey.

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

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

With no annotations, the description must convey behavioral traits. It only states the action without disclosing read-only nature, authentication requirements, pagination, or any side effects. The word 'explore' implies a read operation but this is not explicit.

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 short sentence with no fluff, but it's under-specified. It omits essential guidance about parameters, usage, and behavior, making it more incomplete than concise.

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 3 parameters, no annotations, and a rich set of sibling tools (searchRepos, listRepos, getTrendingRepos), the description is far from complete. It lacks information about return format, filtering semantics, and alternatives, leaving the agent to guess when and how to invoke it.

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 input schema describes limit and category with descriptions, covering 67% of the parameters. The description's phrase 'by category/topic' aligns with the category parameter but adds no insight into limit or relays. The relays parameter remains undocumented in both schema and description.

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 'Explore repositories by category/topic,' giving a clear resource (repositories) and a filter dimension (category/topic). However, the verb 'explore' is vague and could overlap with sibling tools like searchRepos or listRepos, and it doesn't specify the operation's output or scope.

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 usage context is provided. The description doesn't indicate when to use exploreRepos versus searchRepos, listRepos, or getTrendingRepos, nor any prerequisites or limitations.

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

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

With no annotations provided, the description carries the behavioral disclosure burden. It adds meaningful traits: the operation is read-only ('Fetch'), works on public resources, supports specific hosts, can take ~120s when hashing, and is a required precursor to announce. It does not mention rate limits or error behavior, but this is solid coverage for a fetch tool.

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 dense, front-loaded sentences communicate the operation, scope, key optional behavior, and a critical workflow prerequisite. There is no filler or redundant restating of the name.

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?

The description covers the main call pattern and the hash behavior, but there is no output schema and no mention of what a successful response contains (e.g., release metadata, asset URLs, hashes map). It does not explain behavior when no announceable binaries are found, leaving a moderate gap for an agent deciding whether the call succeeded.

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%, so the baseline is 3. The description adds some usage nuance beyond the schema ('required before announce'), but most parameter meaning already lives in the schema, so no strong compensation is needed.

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 precise verb ('Fetch') and resource ('public forge Release'), names the supported forges (GitHub/Codeberg/GitLab), and scopes the result to announceable binaries. This clearly distinguishes the tool from list-oriented siblings like listForgeReleases and listReleases.

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 implies usage context: omit tag for latest, set hash before announce. However, it never explicitly says when to choose this tool over sibling tools such as listForgeReleases or createRelease, so the agent must infer the workflow.

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

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

With no annotations, the description carries the full burden. It reveals that the tool performs an exact forge URL to npub mapping and is GitHub-specific, which is useful behavioral context. However, it does not discuss any other behaviors (e.g., return format, auth, rate limits, error handling) that might differ or be inherited from findReposBySource.

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 two sentences long, front-loaded with the core alias relationship, and contains no filler. Every word earns its place, and the secondary sentence provides essential usage guidance without redundancy.

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 6 parameters with many overlapping names (github/githubs, source/sources), no annotations, and no output schema, the description is too brief to stand alone. It relies on the agent already knowing findReposBySource. It does not explain parameter relationships, defaults, or the return value, leaving significant gaps for a tool with this complexity.

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 only 17% (only 'github' is described). The description adds minimal parameter meaning—the phrase 'exact forge URL' relates to the 'github' parameter but does not explain any of the other five parameters (limit, relays, source, githubs, sources). This is insufficient compensation for the low schema coverage.

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 states it is an alias for findReposBySource and hints at the core function 'exact forge URL → npub'. It distinguishes itself as the GitHub-specific variant by referencing the alternative for non-GitHub forges. However, the arrow notation is cryptic and the actual operation is not fully spelled out.

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 second sentence gives explicit guidance: 'Prefer findReposBySource for non-GitHub forges.' This tells the agent when to use this tool vs the primary alternative. It does not mention other sibling tools like searchRepos or listRepos, but for an alias, the guidance is clear and sufficient.

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

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

With no annotations provided, the description carries the burden of disclosing behavior. It clearly states that it performs exact matching, scans kind-30617 announces, returns npub and gittr URL, and does not fuzzy-match. It omits details like authentication requirements or rate limits, but as a read-only lookup, the disclosed information is reasonably sufficient.

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 three sentences, front-loaded with the core purpose ('Exact reverse lookup'), followed by the return value and use case, and ending with a critical limitation. Every sentence contributes meaning, with no redundant or tangential 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?

The description explains the core purpose, return value (npub + gittr URL), and a key constraint (no fuzzy matching), while parameter details are covered by the schema. It does not describe error cases or pagination behavior, but for a reverse lookup tool with a clear schema, the context is adequately 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 coverage is 100%, so each parameter already has a descriptive definition. The description adds semantic value by clarifying the exact matching intent for the 'source' field, indicating that both forge URLs and GitHub shorthand are accepted, and emphasizing the exact-match behavior, going beyond the schema's basic descriptions.

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 immediately identifies the tool as an 'Exact reverse lookup' and specifies what it matches: forge URLs or GitHub shorthand to find Nostr kind-30617 announces. It clearly distinguishes itself from similar sibling tools by emphasizing exact matching, supporting multiple forge types, and explicitly noting it does not fuzzy-match renamed slugs.

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 gives a clear use case ('so you can DM owners when the forge is unreachable') and states it is for exact reverse lookup, implying a different purpose than search or fuzzy matching. However, it does not explicitly name alternative tools like searchRepos or findReposByGithub, so the 'when-not-to-use' guidance is implicit rather than direct.

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

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Fork an existing repository' does not mention side effects (e.g., creating a new repository), authentication requirements, or effects on the source repository. This is a significant gap for a mutation operation.

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 concise sentence with no filler, fully front-loaded with the essential action. It earns every word.

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 8 parameters, no annotations, and no output schema, the one-sentence description is insufficient. It does not explain the forking workflow, return values, or consequences, leaving the agent without crucial context for a complex operation.

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 75% (6 of 8 parameters have descriptions), so the schema already documents most parameter semantics. The description adds no parameter-specific information, but the coverage is high enough that the baseline of 3 is appropriate.

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 'Fork an existing repository' uses a specific verb (fork) and resource (repository), clearly stating the action. It distinguishes from siblings like createRepo and mirrorRepo, though it doesn't elaborate on the nuances of forking versus those alternatives.

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 forkRepo over alternatives such as mirrorRepo or createRepo. The description simply states the action without context or exclusions, leaving the agent to infer usage purely from the tool name.

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

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Get branches' without explaining return format, authentication needs, side effects, or whether it lists all branches or a filtered set. The verb 'Get' implies a read operation, but no explicit safety guarantees are provided.

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, clear sentence with no redundant wording, making it appropriately concise. However, it is minimal to the point of under-specification, yet it still front-loads the core purpose effectively.

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 lack of output schema and annotations, the description should provide more context about what a branch object looks like, how repositories are identified, and how the 'relays' parameter affects behavior. The current description is insufficient for an agent to fully understand the tool's inputs and outputs.

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 coverage is 67%, with 'relays' lacking any description. The description adds no explanation of parameter purpose or format, leaving the optional 'relays' parameter ambiguous and not compensating for the incomplete schema coverage.

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 states the action 'Get' and the resource 'branches for a repository', making the purpose unambiguous. It is distinct from sibling tools like getRepo or listRepos, but lacks explicit differentiation from similar ref-listing tools such as bridgeListRefs.

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. The description simply states what it does without any context about selection criteria, prerequisites, or when other tools would be more appropriate.

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

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

No annotations are provided, so the description carries the full burden. It merely states 'Get commit history' without disclosing behavior such as default branch handling, pagination limits, whether it is a read-only operation, or the role of the 'relays' parameter. The description adds minimal value beyond the tool's name.

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 concise sentence with no filler words. It is front-loaded with the verb and resource. However, it is slightly under-specifying for a 5-parameter tool, but the conciseness itself is strong.

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 annotations, no output schema, and 5 parameters, the description is too minimal to be complete. It does not explain what the returned commit history looks like, how branches are handled, or what 'relays' means in this context. The description leaves too much for the agent to infer.

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 covers 4 out of 5 parameters (80% coverage), so the baseline is 3. The description itself adds no parameter semantics; it relies on the schema's descriptions for the parameters. The 'relays' parameter lacks a schema description, but the description does not compensate for that gap.

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+resource ('Get commit history') that clearly states the tool's function. It does not explicitly distinguish from siblings like bridgeListCommits, but the term 'repository' provides a distinct context, so it earns a 4 rather than a 5.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that it operates on repository commit history as opposed to bridge commits, nor does it provide any contextual hints about suitable scenarios.

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

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

With no annotations, the description carries the burden of disclosing behavior. It reveals fallback mechanics ('Tries gittr bridge file-content, then a few hardcoded GRASP /raw/ hosts'), a limitation ('Not full Code-tab parity'), and recomended workflow. However, it does not detail error behavior or return value beyond implicit content.

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 three sentences, front-loaded with the core purpose and includes necessary caveats. It is concise but slightly dense with internal jargon like '30617 clone[]', which might reduce clarity for some agents. Still, every sentence contributes.

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 moderate complexity (4 params, no output schema, no annotations), the description covers purpose, usage context, and limitations. It does not describe return format, but that is largely implicit for a file-content tool and the sibling list provides additional context.

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 coverage is 100% with descriptive parameter details (e.g., 'Path to file (e.g., "README.md")'). The description adds little parameter-specific meaning, mainly emphasizing the 'without full clone' approach. This aligns with the baseline for high schema coverage.

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 states the tool's function with a specific verb and resource: 'Get file content without a full local clone.' It also distinguishes itself from siblings by mentioning the gittr bridge and GRASP hosts, and explicitly notes it is not full Code-tab parity, setting it apart from tools like bridgeListFiles.

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 clear context for when to use this tool (when you need file content without a cache) and offers an explicit alternative: 'prefer bridgeListFiles after importRemoteToBridge/mirrorRepo.' It also implies limitations, but does not systematically exclude other scenarios.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only describes the action without revealing what happens if the issue is not found, whether it tries all relays or stops at the first, or any error behavior. This lack of detail is a significant gap for a network-fetching tool.

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, efficient sentence with no filler, front-loaded with the action verb. However, the inclusion of '1621' without explanation could confuse users, slightly reducing clarity while still being concise.

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 fetch tool with no output schema and no annotations, the description is under-specified. It fails to mention the return value, relay behavior when none are provided, error cases, or the meaning of '1621'. A more complete description would cover these aspects to help the agent understand the tool's behavior and output.

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 coverage is 0%, so the description must compensate. It clarifies that issueId is used to fetch the issue, but it does not explain the relays parameter at all—whether it is optional, what default behavior is, or how relay selection works. The description adds minimal value beyond the schema's basic names.

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 states the verb 'Fetch', the resource 'single issue event (1621)', and the identifier 'by id', making the tool's purpose unambiguous. It distinguishes itself from siblings like listIssues (which lists multiple issues) and getPullRequestById (different entity type).

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 implies usage for retrieving a single issue by its ID, but it does not explicitly state when to use this tool instead of alternatives such as listIssues or getPullRequestById. No exclusion or alternative guidance is provided, so the usage context is only implied.

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

Does 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 does not state whether the operation is read-only, whether credentials are needed, or what algorithm is used. It also doesn't mention side effects or return behavior beyond the name.

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 and front-loaded, a single sentence that directly states the action. For a tool with one parameter, this length is acceptable, though it could be slightly more informative without being verbose.

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?

There is no output schema, and the description does not specify the return format (e.g., compressed/uncompressed, hex, base64) or any edge cases. Given the simplicity of the tool, some return details are still necessary for an agent 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 provides 100% coverage for the single parameter (privkey is a 64-char hex private key). The description adds no additional meaning; the phrase 'from private key' merely restates what the parameter already conveys. Baseline 3 is appropriate.

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 states the tool's function: deriving a public key from a private key. It is specific enough to distinguish from any sibling tools, though it doesn't explicitly name alternatives or elaborate on the context of use.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no security warnings. The description is a bare one-liner that provides no usage context.

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

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'from relays,' implying network fetch and no mutation, but omits details like behavior on missing id, error handling, or read-only confirmation. The description is too terse for adequate transparency.

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?

Single sentence, front-loaded with the action and resource. Every word serves a purpose, and the structure is immediately scannable. Exceptionally concise without losing necessary meaning.

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?

The tool is simple, but no output schema or annotations exist. The description covers the core action but lacks return value explanation, error behavior, and relay usage semantics. It's adequate for a straightforward fetch, but leaves gaps for a less inferential agent.

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?

With 0% schema description coverage, the description partially compensates by linking 'by id' to prId and 'from relays' to relays. However, it does not specify parameter formats, constraints, or optionality nuances beyond the schema's bare names. The mental model is basic but functional.

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 specifies the verb 'Fetch' and the resource 'single PR event (1618)' by id, distinguishing it from sibling tools like listPRs (list) and createPR (create). The mention of '(1618)' contextualizes the Nostr event kind, adding domain-specific clarity.

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?

Usage is implied: fetch a single PR by id. It does not explicitly contrast with alternatives (e.g., listPRs) or state when not to use. The description offers minimal guidance on when to choose this over sibling tools.

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

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

With no annotations, the description carries the full burden. It states what information is returned (push cost and paid intent status) but does not disclose whether the operation is truly read-only, requires authentication, or what happens if the paywall is not set up. The 'GET' prefix implies read-only but is not explicit.

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 fluff. It does not waste words, though it is so terse that it omits important context. It earns its place but leaves the reader wanting more.

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, no annotations, and a 7-parameter input schema, this description is severely underspecified. It fails to explain return format, parameter semantics, or usage context relative to siblings, making it inadequate for reliable invocation.

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 7 parameters with 0% coverage in the description, and the description itself mentions none of them. Even though some parameter names are self-explanatory (ownerPubkey, repo), several like ownerBlinkApiKey and ownerLnbitsReadKey need clarification, and the description provides no compensation for the schema's lack of property descriptions.

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 states the tool retrieves push cost and whether the payer has paid intent, using a GET verb against a specific resource. It is distinct from sibling tools like createPushPaywallIntent or syncRepoPushPolicy, though it does not explicitly mention those alternatives.

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 intended usage is implied by the description: checking push payment status and cost. However, it gives no explicit guidance on when to choose this over related tools (e.g., createPushPaywallIntent) or what prerequisites (like having a paywall intent) exist.

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

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

No annotations are provided, so the description must carry the full transparency burden. It only states the retrieval action and identification methods, without disclosing error behavior (e.g., what happens if the repo is not found), authentication needs, relay usage (despite the 'relays' parameter), or return format. This leaves significant behavioral details uncovered for a simple getter.

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 or redundant details. It communicates the core purpose efficiently and earns its place without waste.

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?

The tool is relatively simple (a single repo getter), but with no output schema and no annotations, the description is thin. It does not mention return values, error handling, or the purpose of the 'relays' parameter, making it adequate but with clear gaps. A bit more detail on expected outcomes would improve completeness.

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 already covers 67% of parameters (repoId and ownerPubkey) with descriptions. The description adds the concept of 'owner+name' as an alternative to ID, which aligns with the schema but does not explain the 'relays' parameter. This provides marginal value beyond the schema, but the gap on relays prevents a higher score.

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'), a clear resource ('a single repository'), and explicitly states the two identification methods (by ID or owner+name). This immediately distinguishes it from siblings like listRepos (multiple repos) and searchRepos (search behavior), making the purpose unambiguous.

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 clear context for when to use this tool: when you need one repository and you have its ID or owner+name. It does not explicitly mention alternatives or when not to use it, but the phrasing 'a single repository' naturally contrasts with listing/searching tools, giving implicit guidance.

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

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

No annotations are provided, so the description carries the full burden. It merely says 'Get contributors', which essentially restates the tool's name. It does not disclose whether the result is paginated, what fields are returned per contributor, or whether any ownership/auth checks apply beyond the parameters.

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 extremely concise, using a single six-word sentence that starts with the action and clearly states the object. There is zero filler or repetition, which is ideal for quick parsing.

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 3 parameters, no output schema, and no annotations, a description of this brevity is insufficient. It does not define what 'contributors' means in terms of returned data, how the relays parameter affects behavior, or any error conditions an agent should anticipate. An agent would need to make significant assumptions.

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 67% (two of three parameters have descriptions), so the baseline is 3. The description adds no additional meaning beyond the schema for repoId and ownerPubkey, and it does not explain the optional relays parameter at all.

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 a clear resource ('contributors to a repository'), which immediately conveys the tool's function and distinguishes it from sibling tools like getRepo or listRepos. The tool name reinforces this, making the purpose unmistakable.

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?

There is no guidance on when to use this tool versus alternatives, nor any mention of prerequisites such as the repository existing or the owner having a specific role. With many repo-related sibling tools, an agent gets no explicit direction on selecting this tool or handling edge cases.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get trending/popular repositories' and does not mention authentication, rate limits, the criteria for 'trending', or any side effects. For a tool with no annotation coverage, this is a significant gap.

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 short phrase, which is concise but under-specified. It earns its place as a clear label, but it could easily include a sentence about usage or parameters without becoming verbose.

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?

The tool has no annotations, no output schema, and only a minimal one-line description. The meaning of the relays parameter and the expected response shape are left undocumented, making the context incomplete for an agent.

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 already provides descriptions for limit and timeRange, but relays lacks a description, and the tool description does not compensate. With 67% schema coverage (not high), the description should have clarified the missing parameter, but it adds no parameter information at all.

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 'Get trending/popular repositories' uses a specific verb ('Get') and resource ('repositories'), and the 'trending' qualifier helps distinguish it from sibling repo-listing tools like listRepos or exploreRepos. However, 'popular' is somewhat vague, and no further details are given about what constitutes trending or popular.

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 implies this tool is for when you want trending/popular repositories, but it provides no explicit guidance on when to use it versus the many sibling tools (e.g., listRepos, searchRepos, exploreRepos). No alternatives or exclusions are mentioned.

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

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

No annotations are present, so the description must carry the full burden. It mentions 'refetch' but does not explain side effects (e.g., overwriting existing repos), authentication requirements, or network behavior. The mutation implications are unclear, making this insufficient for a server-side clone operation.

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 that communicates the core action efficiently. However, the term 'refetch' is vague and the sentence is slightly dense, but no words are wasted.

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 annotations, no output schema, and four parameters, this minimal description is insufficient. It does not cover return values, error conditions, prerequisites like credentials, or how this interacts with existing bridge repositories, leaving significant gaps for an agent to invoke 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?

Schema description coverage is 0%, and the description only indirectly adds meaning to cloneUrl ('GitHub/Git URL') and repo ('owner/repo'). It fails to clarify bridgeUrl or ownerPubkey, leaving two of four parameters undefined beyond raw names.

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 states the action ('Server-side git clone into bridge') and the specific resource ('import GitHub/Git URL into owner/repo on gittr'). It distinguishes from sibling tools by focusing on importing external URLs, unlike pushToBridge or mirrorRepo which cover other workflows.

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 implies usage for importing remote git URLs into a bridge repo, but does not explicitly state when to use this tool over alternatives like pushToBridge or mirrorRepo. No exclusions or alternative names are provided.

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

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

No annotations are present, so the description carries full burden for behavioral disclosure. It only states the tool's purpose, with no mention of read-only status, authentication requirements, pagination behavior, return format, or potential side effects. This is insufficient for a tool that presumably fetches data from relays.

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 extremely concise—a single sentence. While this makes it easy to scan, it lacks details that would make the sentence earn its place beyond a basic purpose statement. It is compact but under-specified rather than efficiently complete.

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 that there are no annotations, no output schema, and three parameters including an undocumented one, the description is not complete enough. It fails to explain what the results look like, how relays affect the query, or any constraints like maximum limit. A simple enumeration tool would benefit from a mention of return format or filtering behavior.

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 descriptions cover 'limit' and 'minAmount' but not 'relays'. The description adds no parameter information at all, leaving 'relays' entirely unexplained. With 67% schema coverage and zero compensation from the description, there's a clear gap for the 'relays' parameter and no reinforcement of the covered ones.

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 states 'Discover open bounties' with a parenthetical explanation of what constitutes a bounty (issues with bounty labels or Lightning funding). This is a specific verb+resource with scope, and it distinguishes from the sibling tool listBountiesForIssue, which is issue-specific. However, it doesn't explicitly mention that it returns a list or how results are ordered.

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 like listBountiesForIssue or submitBounty. There is no mention of prerequisites, intended use cases, or exclusions. The description only states what it does, not when to prefer it.

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

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

No annotations are provided, so the description must carry behavioral weight. It only says 'List' and mentions the event kind, but does not disclose return format, pagination, relay behavior, or any side effects. It is a read operation but lacks sufficient detail.

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?

One concise sentence with no filler. Efficiently communicates the core action and target.

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 3 parameters and no output schema, the description is too minimal. It does not explain what kind 9806 events are, how relays are used, or what the response looks like.

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 has zero description coverage, and the description only explains the 'issue id' linkage (issueId parameter). The optional 'limit' and 'relays' parameters are not explained, leaving significant ambiguity.

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?

Description uses specific verb 'List' with resource 'kind 9806 bounty events' and scope 'linked to an issue id'. This clearly distinguishes it from sibling listBounties which likely lists all bounties.

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?

Provides clear context that this tool is for finding bounty events associated with a specific issue ID. However, it does not explicitly mention when to avoid it or mention alternatives such as listBounties.

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

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 states the operation (list), the scope (all forge releases + assets), and a notable non-behavior ('No NIP-82 MIME gate'), plus the gittr Releases tab analogy. However, it does not mention auth requirements, output structure, or potential error/failure modes, which keeps it at a minimally sufficient level.

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?

Three short sentences, each earning its place: the core action, an important technical qualifier about the NIP-82 MIME gate, and a sibling distinction. The primary action is front-loaded and there is no redundant filler.

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 one-parameter read-only listing tool, the description covers the target resource, the scope, the key alternative, and a relevant behavioral qualifier. There is no output schema, so a bit more detail about the exact shape of returned release/asset data could strengthen it, but the description is otherwise sufficient for correct invocation.

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 input schema already provides 100% coverage with 'Forge repository HTTPS URL' for sourceUrl. The description adds no significant new parameter-level meaning beyond using the phrase 'source URL,' so the baseline 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 opens with a specific verb and resource: 'List all forge Releases + assets for a source URL.' It also explicitly distinguishes itself from listReleases, which covers git tags, so an agent can tell which tool fits the need.

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?

It names the direct alternative, listReleases, and gives the selecting condition: listReleases is for git tags while this tool is for forge releases and assets. The note about 'No NIP-82 MIME gate' further clarifies when this tool is appropriate.

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

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It does disclose the NIP-22 kind and root E tag relationship, and it clarifies that bounties are not changed, implying a read-only operation. But it does not mention pagination, relays behavior, or result format, leaving some transparency gaps.

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 two crisp sentences with no filler. The core purpose is front-loaded, and the bounty exclusion is a valuable, relevant clarification that 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?

For a straightforward list tool, the description conveys the essential filtering logic and scope. However, with no output schema, no annotations, and incomplete parameter documentation, an agent still faces meaningful gaps around available parameters and expected response details.

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 only 33%, with only issueId documented. The description adds minimal parameter meaning by explaining the issue id's role, but it says nothing about limit or relays, which the agent would have to infer from names and types.

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 specific verb and resource: 'List NIP-22 comments (kind 1111) on a Nostr issue'. It further clarifies the key technical detail (root E tag = issue id), which distinguishes it from related tools like listPRComments and listBountiesForIssue.

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 clear context by specifying this is for Nostr issue comments and explicitly excludes bounties. However, it does not name sibling alternatives like listPRComments or listBountiesForIssue directly, so the when-not guidance is implicit rather than fully explicit.

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

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

With no annotations, the description carries the full burden of disclosing behavior. It does not mention pagination, return format, authentication, rate limits, or the purpose of the 'relays' parameter. The description is purely syntactic and adds no transparency beyond the tool's name.

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, concise sentence with no wasted words. It is appropriately sized for the simplicity of the operation, though it lacks any additional structured guidance that could aid the agent.

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?

The tool has no output schema and no annotations, so the description should explain return values, filtering behavior, and the role of 'relays'. It does none of this, making the description incomplete for an agent to fully understand invocation outcomes.

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 75%, so the baseline is 3 even though the description itself mentions no parameters. The schema already explains labels, repoId, and ownerPubkey, but the description does not compensate for the undocumented 'relays' parameter, leaving a gap.

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 states the tool lists issues for a repository, using a specific verb and resource. It distinguishes from sibling tools like getIssueById (single issue) and createIssue (creation), and is unambiguous about its scope.

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 such as listPRs or getIssueById. The description merely states the action without context, prerequisites, or exclusions, leaving the agent to infer usage from the name alone.

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

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

No annotations are present, and the description carries the full burden. It usefully exposes the underlying filtering behavior (NIP-22/kind 1111 and root E tag matching), but it does not mention relay behavior, pagination, ordering, or whether comments are fetched live or from cache.

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?

A single dense sentence with no filler. The technical qualifiers earn their place and are front-loaded, making the tool's purpose immediately clear.

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 straightforward read-only list tool, the core operation is clear, but the lack of annotations, no output schema, minimal parameter docs, and no sibling differentiation leave an agent to guess details like relay defaults and result shape.

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 coverage is only 33%: prId is described, but limit and relays are not. The description adds meaning by clarifying that prId is the root E tag, but it does not compensate for the undocumented optional parameters beyond what their names imply.

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 precise verb ('List'), resource ('NIP-22 comments kind 1111'), and scope ('on a Nostr pull request'). The parenthetical 'root E tag = PR id' gives an exact identification rule, so the tool is clearly distinguishable from sibling listIssueComments.

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 intended context is clear: use this to retrieve PR comments. However, it never states when not to use it or points to the sibling listIssueComments as the alternative for issue comments, leaving usage routing to inference.

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

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'List', implying a read operation, but fails to mention return format, authentication needs, pagination, or any other behavioral characteristics.

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, clear sentence with no unnecessary wording, making it appropriately concise and well-structured for a simple list operation.

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?

This is a minimal viable description for a straightforward list operation, but it lacks usage guidance and behavioral details. With no output schema or annotations, the description could be more complete, though it is not severely deficient.

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 describes ownerPubkey and repoId but leaves relays undocumented. The description adds no parameter semantics, and with 67% schema coverage it does not compensate for the gap.

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 ('List') and resource ('pull requests') with a scope ('for a repository'), clearly distinguishing it from sibling tools like listIssues, getPullRequestById, and createPR.

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 such as listIssues or getPullRequestById. It does not mention context, exclusions, or alternative tool selection.

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

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

No annotations are present, so the description carries the full burden. It adds useful behavioral context by scoping the operation to bridge refs/tags/* and clarifying what it is not, but it does not disclose auth requirements, side effects, pagination behavior, or return value details.

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?

Single sentence, front-loaded with the action and resource, with the disambiguation clause earning its place. No filler or redundant repetition of schema information.

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 simple list tool, the description states the exact source and scope and makes the return concept clear: git tags. With no output schema, it could be more explicit about the response shape, but the core calling intent is well covered.

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 75%, so the schema already handles most parameter meaning. The description adds no parameter-specific detail beyond framing the result set as git tags from the bridge.

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 and resource: 'List git tags from the bridge (refs/tags/*)' and explicitly distinguishes this from Zapstore software releases and the website Releases tab. This clearly differentiates it from sibling tools like listForgeReleases or createRelease.

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 gives explicit negative guidance: it is for git tags, not Zapstore software releases or the website Releases tab. This prevents obvious misuse, though it does not name a specific alternative tool to use instead.

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

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Discover' reasonably implies a read-only operation, and the mention of NIP-34 adds useful protocol context. However, it does not explicitly state that the operation is safe, nor does it mention anything about rate limits, side effects, or return behaviors, so it is minimally adequate.

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 two sentences long, front-loaded with the main action, and contains no redundant information. It is appropriately concise for the tool's simplicity.

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 simple list/discovery tool with four parameters and no output schema, the description is adequate but leaves gaps. It does not mention the default limit, the optional nature of relays, or how this relates to other discovery tools, but the schema covers the parameter details. The description could be richer in explaining what the agent should expect when invoking it.

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 input schema covers 100% of the parameters with descriptions, so the baseline is 3. The description adds a slight nuance by summarizing that filtering is by 'pubkey or search term,' which helps convey the purpose of two parameters, but it does not compensate fully for the lack of any additional meaning beyond the schema.

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 'Discover' and clearly identifies the resource ('repositories from Nostr relays (NIP-34)') and the filtering capability. It is clear in its intent but does not explicitly distinguish itself from sibling tools like searchRepos or exploreRepos, so it falls short of a 5.

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 no guidance on when to use this tool versus alternatives such as searchRepos, exploreRepos, or myRepos. It simply states what it does without any context on preferred use cases or exclusions, offering no help in tool selection.

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

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

With no annotations, the description carries the full burden. It discloses the internal Nostr event mechanism (kind 7 with #k 30617) and the 'latest reaction per repo wins' rule, adding meaningful behavioral context. It does not mention side effects, but 'list' implies a read-only operation.

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 dense sentence, front-loaded with the main action and followed by a compact parenthetical with technical details. There is no fluff or repetition.

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?

The description gives the core purpose and some technical context, but lacks an output format description and does not explain the relays parameter. With no output schema and no annotations, the description is adequate for an expert but leaves gaps for a general AI agent.

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 only 50% (relays is undocumented). The description adds no parameter information at all, leaving the relays parameter unexplained. It fails to compensate for the schema gap, even though the schema's pubkey description mentions auto-detection.

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 states it lists starred repos, using the specific verb 'List' and the resource 'repos a user starred'. It also adds technical detail about event kind and dedup logic, which distinguishes it from siblings like listWatchedRepos.

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 implies usage for listing starred repos but does not explicitly compare with alternatives or state exclusions. It lacks guidance on when to choose this over listWatchedRepos or other list tools, leaving usage inferred from the tool name and phrasing.

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

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

There are no annotations, so the description carries full disclosure burden. It does add meaningful context that the data comes from the 'latest kind 10018 followed-repos event' on relays rather than a live repository list, but it omits details like error behavior, default relay handling, and return format.

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 words. It efficiently communicates the action and the data source without redundancy.

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 annotations, no output schema, and only a minimal description, the tool lacks crucial context like expected output shape, whether pubkey is required, what happens if no followed-repos event exists, and how relays are used. This makes it incomplete for an agent to invoke confidently.

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 and no per-parameter documentation. The description only vaguely hints at 'your' (suggesting pubkey) and 'on relays' (suggesting the relays array), but it does not explicitly explain the semantics or required format of either parameter.

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 'List' plus a specific resource ('repos from your latest kind 10018 followed-repos event on relays'), clearly identifying what the tool does. It also distinguishes itself from siblings like listRepos and myRepos by referencing the Nostr event type.