query_records

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

No annotations provided, so description carries full burden. Discloses truncation behavior and grouping aggregation. However, does not mention return format, permissions, or rate limits. Adequate but could be richer.

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?

4 sentences, front-loaded with purpose, efficient. Every sentence adds value. Could be slightly more structured but overall concise.

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 query tool with 6 params and no output schema, description covers key aspects: data format, grouping, filtering, date range, limit, truncation, and reference to list_sources. Complete for typical usage scenarios.

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 coverage is 100%, baseline 3. Description adds meaning beyond schema by explaining the data structure (one row per date x source x category) and that grouping aggregates sums. Provides context for source/category filtering via list_sources.

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 clearly specifies 'Query raw daily activity records' with detail on data structure (one row per date x source x category: minutes, raw_value, raw_unit). Distinguishes from siblings like get_recent_activities by focusing on raw daily records with filtering and grouping.

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?

States requirement for from/to date range, suggests filtering by source/category with reference to list_sources, and provides guidance to prefer grouping for ranges over ~2 months to keep output small, mentioning raw mode cap and truncation. Does not explicitly contrast with siblings but gives clear context.

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