get_my_metrics

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. Discloses private nature, plan requirement, and return metrics. Falls short of detailing exact behavior like read-only (implied), error states, or rate limits. Adequate but not comprehensive.

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?

Description is a single paragraph with no fluff. Every sentence adds information: what, defaults, requirements, and usage hint. Could be slightly more structured (e.g., separate prerequisites), but effective.

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?

Despite no output schema or annotations, the description covers all essential aspects: what metrics are returned, default time range, parameter behavior, prerequisites, and suggested combination with other tools. Comprehensive for a data-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?

Schema covers 100% of parameters, baseline 3. Description adds value beyond schema by explaining 'app' as 'Partner app id from get_my_apps (omit for all your apps)' and clarifying date defaults (30 days ago, today).

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?

Description uses specific verb 'get' and resource 'metrics' with clear scope ('YOUR OWN private daily Partner Dashboard metrics'). Distinct from sibling tools like 'get_top_apps' (public) and 'search_apps' (public), making selection 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?

Provides key context: defaults to last 30 days (max 366), requires PartnerLens Unlimited plan with Shopify integration, and suggests combining with public tools for comparison. Lacks explicit 'when not to use', but the contrast with sibling tools is implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.