get_daily_activity

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

Discloses error behavior (SuuntoNotFoundError for unsynced dates, 404 without subscription) and declares tool as read-only. Provides actionable guidance on reliable dates.

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?

Single paragraph with front-loaded purpose, followed by fields, error conditions, alternative, and prerequisites. No redundant sentences.

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 single-parameter read tool, description covers purpose, return values (fields listed), error cases, usage notes, and alternatives. No output schema, but fields are enumerated.

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 already covers date parameter fully (format, examples, description). Description adds context on sync timing and error likelihood, slightly enriching the schema's baseline.

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?

States the tool returns a 24/7 activity summary for a single day and lists the exact fields. Differentiates from sibling list_daily_activity by contrasting single day vs. date range.

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 tells when to use (single day fetch), when not to use (future/today likely error), and provides alternative (list_daily_activity for ranges). Mentions subscription prerequisite.

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