Get information about Follow On Tours — who we are, what we sell (bespoke cricket and golf travel), our experience, our financial protection, and how the service works. Use this when someone asks who Follow On Tours is, whether they cover a sport or destination, or how the service operates.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. 'Get information' implies a safe read operation, and the listed content gives a good sense of what the tool returns, but it doesn't explicitly state that no data is mutated or describe any limitations or edge cases. For a simple read-only tool this is adequate but slightly 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?
Two well-structured sentences with no filler. The first sentence explains what the tool provides, and the second gives practical usage conditions. Every word contributes to agent comprehension.
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?
For a parameterless read-only information tool with no output schema, the description covers the subject matter thoroughly and gives clear usage guidance. It doesn't describe the exact return format, but that's a minor omission given the simple nature of the tool.
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, so the schema already fully covers this dimension (100% coverage). The description doesn't need to add parameter-level detail; the baseline of 4 applies.
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 verb ('Get information') and resource (Follow On Tours), and enumerates the exact topics covered (who they are, what they sell, experience, financial protection, how the service works). Even without siblings, the purpose is wholly unambiguous.
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 says 'Use this when someone asks who Follow On Tours is, whether they cover a sport or destination, or how the service operates,' which gives clear trigger conditions. There are no siblings to contrast with, so a 'when not to use' clause isn't applicable.
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.
With only one tool, there is no possibility of confusing it with others. The purpose of get_about is clear and distinct by virtue of being the sole tool.
The single tool name follows a verb_noun pattern (get_about). Since there is only one tool, there is no inconsistency or mixed conventions to evaluate.
The server has only one tool, which is far too few for a travel-focused service. Even if its purpose is limited to company information, the name 'cricket-travel' implies a broader toolset, making this feel under-scoped.
The server only provides an about/info tool. There are no tools for searching tours, viewing itineraries, checking availability, or making bookings—leaving major gaps in the core functionality implied by the server name and description.