List Kimai Activities

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

Annotations already provide rich behavioral information (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=true). The description adds that it uses the /api/activities endpoint and is read-only, which aligns with annotations but does not significantly expand beyond them. No contradictions.

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?

Two concise sentences. The first sentence front-loads the action, resource, endpoint, and optional filter. The second sentence states read-only nature. No wasted words.

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 description does not explain return format, pagination behavior, or the effect of the 'response_format' parameter. Given 8 parameters and no output schema, some additional context about what the response contains would be helpful. However, annotations and schema provide substantial context.

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 coverage is 100%, so the schema fully documents all 8 parameters. The description only hints at the 'project' parameter for filtering. While the schema descriptions are adequate, the tool description adds minimal value beyond what the schema already provides.

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 verb 'List', the resource 'activities', the endpoint '/api/activities', and indicates optional filtering by project. This distinguishes it from sibling tools like kimai_get_activity (single activity) and kimai_list_timesheets (different entity).

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?

The description mentions 'This tool is read-only', which is a usage hint. It implies that the tool is for listing activities and can be filtered by project, but it does not explicitly specify when to use this tool versus alternatives like kimai_get_activity. However, the name and context provide sufficient guidance.

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