list-endpointsLists all API paths and their HTTP methods with summaries, organized by path. Results can be passed directly into 'get-endpoint'.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds that results are organized by path and include methods and summaries, which is useful but does not disclose potential large result sets or any ordering guarantees. Since the schema has no parameters, the description shares the burden of explaining behavior, but the added detail is modest.
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 exactly two sentences, front-loaded with the main purpose, and contains no fluff. Every phrase earns its place by specifying scope, content, and downstream usage.
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 with no parameters and no output schema, the description adequately conveys what is returned (paths, methods, summaries) and how to use the results (feed into get-endpoint). It does not detail the summary format or mention size limits, but given the low complexity, this is sufficient.
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 zero parameters, the schema coverage is trivially 100%. The description needs no parameter explanations, and the baseline for zero parameters is 4. The description adds no unnecessary parameter information.
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 all API paths and their HTTP methods with summaries, organized by path.' This is a specific verb (list) with a specific resource (all API endpoints) and clearly differentiates from siblings like 'get-endpoint' (singular) and 'search-endpoints' (filtered).
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 context for use by noting that results can be passed into 'get-endpoint', which implies a workflow for exploring endpoints. However, it does not explicitly contrast this with 'search-endpoints' or when to choose one over the other, so it is not a full 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct role: list-endpoints enumerates all paths, search-endpoints finds specific ones, get-endpoint retrieves details, execute-request makes actual API calls, and pay-with-x402 handles payment. There is no real overlap between these actions.
Most tool names follow a consistent lowercase verb-first hyphenated pattern (execute-, get-, list-, search-). pay-with-x402 is a minor deviation with a phrasal verb, but it still maintains the overall verb-led style.
Five tools is an appropriate count for a focused API client server. Each tool serves a distinct purpose in the discovery-to-execution workflow, earning its place without excess or deficiency.
The tool set covers the complete workflow: discovering endpoints, getting endpoint details, managing access via payment, and executing requests. This allows agents to fully explore and call any Vybe API endpoint with no obvious dead ends.