Retrieves the official ConnectMeGuru grounding knowledge base, including installation guides, device compatibility, refund policies, and support escalation workflows.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must convey behavioral traits like read-only. While the name and content suggest a safe read, the description does not explicitly state it is non-destructive or idempotent, leaving ambiguity.
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?
Single sentence with no wasted words. Immediately states the core function and lists key contents. Front-loaded and efficient.
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 zero parameters, no output schema, and a clear list of knowledge base topics, the description is adequate. However, it lacks an explicit mention of being a read-only operation, which would complete the behavioral contract.
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?
No parameters exist, and schema coverage is 100% trivially. According to rubric, 0 params yields baseline 4. No parameter documentation needed.
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?
Description uses specific verb 'Retrieves' and identifies the resource 'official ConnectMeGuru grounding knowledge base' followed by concrete content examples (installation guides, refund policies). It clearly distinguishes from sibling tools that handle orders, purchases, and verification.
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 usage when the agent needs knowledge base information, and sibling tools cover transactional actions. No explicit when-not or alternatives, but context makes it clear.
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: order management, catalog browsing, wallet operations, authentication, and support. No two tools have overlapping purposes, making selection unambiguous.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., get_esim_catalog, purchase_esim_with_wallet, verify_agent_otp). There is no mixing of conventions.
With 14 tools, the surface is well-scoped for an eSIM service: catalog browsing, purchasing, wallet management, authentication, order history, and support. No tool feels redundant or missing.
The set covers the core eSIM lifecycle (browse, buy, cancel, top-up, monitor usage, wallet, auth, support). A minor gap is the lack of a dedicated tool to retrieve a single order detail beyond the paginated list, but agents can work around.
