axonhub_list_projectsList AxonHub projects with status and pagination support. Use 'after' and 'first' to control result size and navigate to the next page.
List AxonHub projects with status and pagination information.
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | Pagination cursor returned by a previous call. | |
| first | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the behavioral disclosure burden. 'List' implies a read operation, and 'with status and pagination information' gives some return-shape context. However, pagination mechanics, defaults, limits, and other behavior are left unsaid, so the disclosure is only partial.
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, front-loaded sentence with no filler. Every word carries signal: resource, output contents, and pagination are all named.
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 with no annotations and no output schema the description needs to explain return semantics and optional parameters more fully. It only states that status and pagination info are included, leaving the meaning of 'first' and pagination behavior unexplained.
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%: 'after' has a description, but 'first' has none. The tool description mentions pagination information but never explains that 'first' is the page size or how it interacts with the cursor, so it does not meaningfully compensate for the undocumented 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 names the exact verb and resource ('List AxonHub projects') and adds that results include status and pagination information. This clearly differentiates it from sibling tools like axonhub_list_channels and axonhub_list_models by resource.
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 the siblings, when not to use it, or what alternatives exist. The sibling names are present in context, but the description itself never mentions them or any selection criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.