List all Convalytics projects on the team this token belongs to. Useful when the agent needs to confirm the project it's querying against. No arguments.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, making the safety profile clear. The description adds scope context (team/token) but does not go beyond what annotations provide for behavioral disclosure.
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 concise sentences with no redundancy. The first states the purpose, the second provides usage guidance. Every word earns its place.
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, read-only list tool with no parameters and no output schema, the description covers essential context. Though it could mention the output format (e.g., list of project names/IDs), it is complete enough given the tool's simplicity.
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 with 100% schema coverage (empty object). The description explicitly states 'No arguments.' which is clear and sufficient, earning baseline 4 for zero parameters.
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 'List all Convalytics projects on the team this token belongs to.' This specifies the verb (list) and resource (projects), and distinguishes itself from sibling tools which deal with funnels, events, and pageviews.
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 states when to use: 'Useful when the agent needs to confirm the project it's querying against.' This provides clear context, although no exclusions or alternatives are mentioned.
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.
All tools have clearly distinct purposes. Funnel operations (compute, create, delete, get, list, update) are well-separated from event tools (events_count, recent_events) and pageview tools (pageviews_count, top_pages, top_referrers). Composite snapshots (user_activity, weekly_digest) and utility tools (get_usage, list_projects) are unique.
Naming pattern is inconsistent: some tools use verb_noun (compute_funnel, create_funnel), others noun_verb (events_count, pageviews_count), and some are adjective_noun (recent_events, top_pages) or noun_noun (user_activity, weekly_digest). While readable, the lack of a consistent convention reduces predictability.
15 tools is at the upper boundary of 'well-scoped' but still appropriate for an analytics platform. Each tool serves a necessary function without unnecessary duplication, though a few more could be justified.
The tool set covers core analytics operations: CRUD for funnels, event and pageview counting, top pages/referrers, user and weekly snapshots, and project/usage info. Minor gaps exist (e.g., no session-level detail), but overall it addresses common analytics queries well.
