get_activity_types

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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description largely repeats that with 'read-only.' The note 'Dates are YYYY-MM-DD' is irrelevant because the tool has no date parameters. No additional behavioral context, such as list size or whether the result is cached, is provided.

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 core sentence is short and front-loaded. The parenthetical is partly redundant with the annotations and partly irrelevant, so the description is not maximally efficient, but it remains compact.

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?

An output schema exists, so return values need not be explained in the description. With safety covered by annotations and no parameters, the description is mostly sufficient, though missing usage context keeps it from being fully complete.

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?

This tool has zero parameters, so the schema baseline is 4. The description adds no meaningful parameter semantics; the date-format note does not correspond to any input and could be mildly distracting.

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 gives a specific verb and resource: it returns all activity types plus their parent types. That clearly separates it from activity-listing siblings such as get_activities. However, it does not explicitly contrast itself with those tools, so it falls short of a perfect score.

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 explicit when-to-use guidance or mention of alternatives. The reference-list nature of the tool is implied by 'Return all activity types,' but an agent gets no direction on whether to call this before activity queries or how to use the parent-type information.

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