Retrieve paginated products or services from KikoBooks. Search by name or description to quickly find specific items for accounting tasks.
List products/services (items) from KikoBooks. Returns paginated results with search support.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (default: 1) | |
| search | No | Search by item name or description | |
| pageSize | No | Results per page (default: 50, max: 500) |
Changes observed during successful MCP inspections.
v0.2.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses pagination and search support, which is useful, but says nothing about read-only nature (only implied by 'List'), permissions, or result scope. For a zero-annotation tool this is thin.
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 short sentences, front-loaded with the resource and followed by the return behavior. Efficient with no wasted words.
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 and no output schema, the description should do more: it omits how items relate to get_item, what fields are returned, and any caveats. It is under-specified for a tool an agent must route correctly among many search_* siblings.
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 page, search, and pageSize are already documented. The description's mention of 'search support' loosely maps to the search parameter but adds no syntax or format detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.
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?
States a specific verb (List) and resource (products/services, i.e. items) and names the source system (KikoBooks). An agent can tell it deals with items, but it does not explicitly differentiate from the closely-related get_item sibling or from the other search_* 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 gives no when-to-use guidance, no conditions for choosing search over get_item, and no exclusions. Usage must be inferred entirely 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.