get_platform_infoExplain how iTutorOnline works: pricing, the free first 30 minutes, hour packages, languages of instruction, how booking works, and the live count of verified tutors.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is known. The description adds context about the content covered but does not reveal additional behavioral traits beyond what annotations provide.
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 sentence that efficiently lists the key information areas. It is front-loaded with the core purpose and uses minimal words to convey scope.
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's simplicity (no parameters, no output schema), the description covers all essential aspects of what information the tool provides. It is complete for its intended use.
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 input schema has no parameters, and schema description coverage is 100% (trivially). The description adds no parameter details because none exist, but it clarifies the tool's purpose. Baseline 4 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?
The description clearly states the tool explains how iTutorOnline works, listing specific topics (pricing, free trial, packages, languages, booking, live tutor count). The verb and resource are specific, and it distinguishes from sibling tools that focus on individual tutors or bookings.
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?
While the description does not explicitly state when to use versus alternatives, the context makes it clear that this tool is for general platform information. The list of sibling tools helps differentiate usage, but no explicit exclusions or when-not guidelines are provided.
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 addresses a distinct task: info, search, profile detail, reviews, subjects, self-serve booking prep, and human-assisted requests. Even the two booking-related tools are clearly separated by their descriptions and outcomes.
All tools follow a consistent lowercase snake_case verb_noun pattern such as get_tutor, list_subjects, search_tutors, prepare_booking, and request_human_tutor. The naming makes the function of each tool predictable.
Seven tools is a well-scoped set for a tutoring platform integration. Each tool addresses a meaningful part of the user journey without redundancy or bloat.
The surface covers platform info, discovery, evaluation, subject lookup, and both self-serve and human-assisted booking paths. A minor gap is the absence of direct booking management or tutor availability checks, but these are not required for the primary workflow.