get_home_summary

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

No annotations are provided, so the description must fully disclose behaviors. It only states what data is returned, but omits critical details such as whether the operation is read-only, auth requirements, rate limits, or the effect of the timezone_offset parameter. For a tool with zero annotations, this is insufficient.

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?

The description is a single sentence, making it concise. However, it sacrifices essential information (parameter semantics, usage context) for brevity. It is not well-structured to front-load the most critical details.

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?

The tool has a simple output schema, but the description omits the input parameter entirely. Given the low tool complexity and presence of output schema, the description is minimally adequate but lacks completeness regarding the timezone_offset parameter.

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 description coverage is 0%—the description does not mention the only parameter (timezone_offset). It adds no meaning beyond the schema, failing to explain its purpose or default value. With low coverage, the description should compensate but does not.

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 the tool retrieves dashboard summary statistics, listing specific examples (total workouts, weight, streak). This differentiates it from sibling tools like get_home_chart and get_home_muscle, which likely return different data.

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?

No guidance on when to use this tool versus siblings like get_home_chart or list_enrolled_programs. No context on prerequisites, expected states, or alternative tools.

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