Find vendors in KikoBooks by name or company and return paginated results for accounting and bookkeeping tasks.
Search vendors in KikoBooks. Supports text search by name or company. Returns paginated results.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (default: 1) | |
| search | No | Search by vendor name or company | |
| 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 that search is by name or company and that results are paginated, which is mildly useful, but says nothing about sorting, result limits, or what a match returns. For a search tool with zero annotation coverage, 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?
Three short, front-loaded sentences with no filler. Efficient, though 'in KikoBooks' is redundant given the toolset context.
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?
A search tool with no annotations and no output schema should explain what happens when search is omitted, how results are ordered, and roughly what is returned. The description omits all of that, leaving the most consequential behaviors undocumented.
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 schema already documents all three parameters including defaults and max. The description's mention of name/company text search and pagination adds no syntax or format beyond the schema, so 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?
States a specific verb (Search) and resource (vendors) scoped to KikoBooks. It distinguishes itself from read tools like get_vendor but does not differentiate from the large family of sibling search_* tools beyond the resource name, which the tool name already conveys.
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 on when to use this versus get_vendor or the other search_* tools. It mentions pagination but offers no conditions, prerequisites, or exclusions. Usage is left entirely to inference from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.