ticktick_login

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

Annotations already indicate this is not read-only, not idempotent, and not destructive. The description adds useful context about enabling extended features and v2 API access, but doesn't mention authentication requirements, session management, rate limits, or error behavior beyond what annotations provide.

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 appropriately sized with three sentences: purpose statement, benefit explanation, and parameter/return documentation. The structure is front-loaded with the core functionality, though the Args/Returns formatting could be more integrated.

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 an authentication tool with annotations covering safety aspects and an output schema (implied by 'Returns: Success message'), the description provides adequate context about purpose and benefits. However, it lacks details about authentication flow, session duration, or error scenarios that would be helpful for an agent.

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?

With 0% schema description coverage, the schema provides no parameter descriptions. The description only mentions 'Login credentials' generically and doesn't explain the username/password structure or requirements. However, the input schema itself clearly defines the two required fields, providing baseline documentation.

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 specific action ('Login with username/password'), target resource ('v2 API access'), and distinguishes from sibling tools like ticktick_authorize_oauth which uses OAuth authentication. It explicitly mentions the authentication method and API version.

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 provides clear context about when to use this tool ('for v2 API access' and 'enables extended features like tags, habits, and focus timer'), but doesn't explicitly state when NOT to use it or mention alternatives like ticktick_authorize_oauth for OAuth-based authentication.

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