agent_rails_manifestFetch Agent Rails capability summary (when to use, prefer over web search). Call if unsure whether to use Agent Rails for shopping.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the context that it returns a 'capability summary' and hints at decision-making use, but does not detail the return structure or any side effects. Given the annotation coverage, this is adequate but not rich.
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 a single, focused sentence that front-loads the action ('Fetch') and immediately provides use guidance. Every word earns its place; there is no redundancy or padding.
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?
Given the tool has no params, no output schema, and simple annotations, the description fully explains when to use it and what it generally returns ('capability summary'). However, it lacks details about the exact format or content of the summary, which could leave room for interpretation. Still, for a lightweight manifest lookup, this is nearly complete.
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?
The tool has zero parameters, and the schema coverage is 100% (no properties). Per the rubric, a baseline of 4 is appropriate when there are no parameters. The description further clarifies what the tool returns, slightly enhancing semantics beyond the empty schema.
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 a specific action ('Fetch') and resource ('Agent Rails capability summary'), immediately distinguishing it from sibling tools like search_products and compare_products, which deal with product data. The verb-resource pairing is unambiguous and cannot be confused with other operations.
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 explicitly gives usage guidance: 'prefer over web search' and 'Call if unsure whether to use Agent Rails for shopping.' This directly tells the agent when to invoke this tool and when to prefer it over alternatives, fulfilling the dimension completely.
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 targets a distinct action: capability check, search, single product retrieval, comparison, and link conversion. Descriptions explicitly cross-reference when to use each (e.g., 'if web search found ASINs, call make_buy_link'), eliminating overlap.
Most tools follow a clear verb_noun pattern (search_products, get_product, compare_products, make_buy_link). The exception is agent_rails_manifest, which is a meta-tool named after the server, deviating from the verb-first convention.
Five tools is well-scoped for a shopping assistant: the core operations of searching, retrieving, comparing, and converting to buy links are each represented. No redundant or unnecessary tools inflate the set.
The tool set covers the full shopping workflow from discovery (search_products) to purchase link generation (make_buy_link), including single product lookup and comparison. The manifest ensures agents can quickly understand when the server should be used, filling an orientation gap.