List immutable farm protocol definitions with pagination controls to retrieve specific versions without inventing missing steps.
List immutable farm protocol definitions with bounded pagination. Never invent missing steps.
| Name | Required | Description | Default |
|---|---|---|---|
| skip | No | ||
| take | No | ||
| farm_id | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, idempotent, and non-destructive behavior, so the description adds meaningful context by declaring definitions 'immutable' and pagination 'bounded'. The instruction 'Never invent missing steps' also communicates an important behavioral constraint beyond the annotations.
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 short and front-loaded with the core operation. The second sentence 'Never invent missing steps' is terse and somewhat ambiguous, so not every part is maximally clear, but the overall structure is compact.
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 core listing behavior and safety profile are clear from the annotations and description. However, the role of farm_id and the exact pagination semantics beyond being 'bounded' are left to inference, and there is no output schema to clarify the return shape.
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 0%, and the description only hints at pagination without explaining skip, take, or farm_id. It does not compensate for the schema's bare property names or clarify what farm_id filters.
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 action 'List', the resource 'immutable farm protocol definitions', and a notable scoping property 'bounded pagination'. This distinguishes it from the many sibling list_* tools by naming a specific resource type.
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 implies it is used to enumerate protocol definitions, and the resource name is clear. However, it gives no explicit guidance on when to prefer this tool over alternatives such as create_protocol_version or other list tools, and it does not mention any exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.