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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds real behavioral context beyond that: the default status=open filter, the four distinct endpoints reached depending on inputs, and the 100-per-page pagination size.

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?

Four short sentences, front-loaded with the resource definition and scoping before the endpoint detail. The endpoint enumeration is somewhat verbose but earns its place by mapping inputs to routes.

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?

No output schema exists, so the description should carry return-value context; it gives pagination size and hints at next_page handling in the schema. It stops short of naming returned fields, leaving a modest gap.

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 baseline is 3. The description still adds value by stating what happens when project_id is omitted ("across all projects") and reinforcing the status default, which the schema only hints at.

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?

States a specific verb+resource ("List Tick tasks") and even clarifies the domain concept ("budget lines that time entries are logged against"), which an agent cannot get from the name alone. The scoping rules make it easy to distinguish from sibling list tools like tick_list_projects or tick_list_entries.

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?

Explains the two scoping modes (all projects vs. one via project_id) and the default filter (open tasks). It also ties the tool into the logging workflow ("You need a task id to log time"), but it never explicitly names a sibling alternative or a when-not-to-use condition.

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