Retrieve the FAA (Free App Analytics) Terms of Service document link.
Use this tool when the user wants to review the Terms of Service before creating an FAA account. Returns a clickable link to the TOS document and instructions for account creation.
Example: kochava_free_app_analytics_get_tos()
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It states it returns a clickable link and instructions, implying no side effects. However, it doesn't explicitly confirm read-only behavior, but given the nature, it's sufficiently transparent.
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?
Concise at 2-3 sentences with an example. No fluff, front-loaded with purpose.
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 and an output schema, the description adequately explains the tool's purpose and return value. No missing context for a simple retrieval 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?
No parameters, so baseline 4. Description adds no param info, but none needed. Schema coverage is 100%.
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 it retrieves the FAA Terms of Service document link, which is a specific verb+resource. It distinguishes from the sibling tool (create account) by specifying the purpose of reviewing TOS before account creation.
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?
Explicitly says when to use: when user wants to review TOS before creating an FAA account. Provides context but no explicit when-not-to-use or alternatives, though the sibling tool is implied as the next step.
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.
The two tools have clearly distinct purposes: one retrieves the Terms of Service, the other creates an account. No overlap or ambiguity.
Both tools share the 'kochava_free_app_analytics_' prefix and follow verb_noun pattern, though one uses 'create_acc_and_get_auth_key' and the other 'get_tos'. Mostly consistent with minor variation in verb complexity.
With only 2 tools, the server feels very thin for a typical MCP server. It covers only account creation and TOS retrieval, lacking other expected functionalities.
The tool surface covers only account creation and TOS viewing. Missing tools for managing accounts, viewing analytics, or performing other common advertiser tasks, leaving significant gaps.
