Get aggregate statistics about missions on the HomeVisto platform. Returns total counts, status breakdown, and average bounty information. Useful for understanding platform activity.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, setting the safety baseline. The description adds value by disclosing specific returned metrics (total counts, status breakdown, average bounty). No other behavioral caveats are needed for a parameterless read-only tool.
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 two sentences. The first sentence states the action and resource, the second lists outputs and use case. Every word is purposeful, with no repetition of annotations or schema fields.
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 simple, parameterless, read-only aggregation tool, the description fully covers what it does, what it returns, and its utility. With no output schema and zero parameters, there is no missing critical information.
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?
With zero parameters, the schema is fully self-descriptive. The description doesn't need to explain parameters, and the baseline for no-parameter tools is 4. The text adds contextual meaning about the aggregate nature 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 specifies a clear verb ('Get') and resource ('missions'), explicitly stating aggregate statistics. It distinguishes from sibling tools by focusing on platform-wide aggregates rather than individual missions or searches.
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 gives a clear context ('useful for understanding platform activity') and implies this is the overarching dashboard tool. It doesn't explicitly exclude cases for sibling tools, but the aggregate nature makes the appropriate use case obvious.
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 serves a clearly distinct purpose: retrieving a single mission by ID, viewing aggregate stats, finding missions by geographic proximity, listing missions with filters, and searching by keyword. The descriptions clearly differentiate these use cases, so an agent would have no trouble selecting the correct tool.
All tools use snake_case with a verb-noun pattern, but the verbs vary: get_ for retrieval, list_ for paginated browsing, and search_ for keyword lookup. This is a minor inconsistency, but the pattern is still predictable and readable.
Five tools is well within the ideal range for a focused mission discovery server. Each tool adds meaningful functionality without redundancy or bloat.
The server covers the read side of mission discovery thoroughly: single item retrieval, list, search, geo search, and statistics. Write operations like creating, updating, or accepting missions are missing, but the descriptions suggest this is intentionally a read-only browsing tool for scouts.
