get_activity_details

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds no behavioral context of its own (no scope, no payload shape, no caveats). The single sentence is purely about parameter defaults, which belongs to the parameter layer, not behavior.

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?

It is short, but it is a dangling fragment with no subject or verb, so brevity is the result of under-specification rather than tight writing. Nothing about the tool's purpose is front-loaded because no purpose is stated at all.

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?

With no output schema, three parameters, and no annotations beyond read-only/open-world, the description is the only place purpose and return content could be explained, and it omits both entirely. An agent cannot tell what this returns or why it differs from get_activity.

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 only 33% (only activityId is documented as 'Numeric id'), so the description must compensate. It does partially: it supplies the defaults maxchart=2000 and maxpoly=4000 and maps them to the wire names maxChartSize/maxPolylineSize. However it never explains what those sizes control (chart data resolution? polyline point count?) or the accepted units/ranges.

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 never states what get_activity_details does. It opens with parameter defaults and reads like a fragment of schema documentation rather than a description of a tool. Against siblings such as get_activity, get_activity_splits, and get_activity_weather, an agent has no basis for telling this tool apart.

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?

There is no when-to-use guidance, no mention of alternatives, and no indication of what kind of 'activity details' this returns versus the many other get_activity_* siblings. Nothing routes the agent to or away from this tool.

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