list_activities

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

The description adds only the endpoint 'GET /activities' and the phrase 'all activities.' Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so no unsafe behavior is hidden, but the description doesn't disclose filtering, ordering, pagination, or payload size implications. It adds little beyond the annotations.

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 two lines: a clear imperative sentence and the exact endpoint. Every word earns its place and the core information is front-loaded with no waste.

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 zero-parameter, read-only listing tool with a full output schema and four annotations covering safety, this is effectively complete. An agent can call it without missing critical information, though a sentence clarifying what 'activities' includes would push it to a 5.

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?

The tool takes zero parameters, so there is nothing for the description to clarify. The input schema already reflects this fully, and the rubric's baseline for a zero-parameter tool is 4.

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 states the verb 'Get' and the resource 'all activities', making the tool's purpose immediately clear. It doesn't explicitly differentiate from sibling list tools, but the resource 'activities' is distinct enough that the name carries much of the differentiation.

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 is given on when to use this tool versus alternatives. The sibling list includes delete_activities_by_activity_id for targeted operations, but the description provides no context about when listing all activities is appropriate or how it relates to other list endpoints.

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