List reviewed local SentenceTransformer models without contacting a registry. Solve offline availability issues by using locally cached model metadata.
List reviewed local SentenceTransformer models without contacting a registry.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.7.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the operation is read-only ('List') and that it avoids network calls ('without contacting a registry'). However, it does not mention potential side effects, performance characteristics, or what happens if no models are reviewed.
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 is front-loaded with the action and resource. Every word adds value, and there is no fluff or repetition. It is as concise as possible while still 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?
Given the tool's simplicity (no parameters, output schema exists), the description covers the essential purpose and behavioral constraint. It tells what the tool lists and that it is local/offline. The presence of an output schema means the return format is handled elsewhere, so the description is sufficiently 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?
The input schema has zero parameters, so the description does not need to add meaning beyond the schema. The baseline for no parameters is 4. The description does not introduce any additional parameter understanding, which is acceptable.
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 clearly identifies the resource ('reviewed local SentenceTransformer models'). It also adds a distinguishing constraint ('without contacting a registry'), which helps differentiate it from sibling tools that might involve registry or network calls.
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 some context about when to use this tool (listing models without a registry call), but it does not explicitly state when not to use it or mention alternative tools. No guidance is given for scenarios where models might need to be fetched from a registry or filtered.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.