ticktick_get_by_id

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

With no annotations provided, the description carries the full burden, and it delivers. It discloses the empty-object return for missing IDs, the error envelope on failure, and the critical cache-freshness behavior with a sync threshold and a remedy. This goes well beyond what the tool name or schema reveals.

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 organized into useful sections: Args, Returns, Freshness, and Example. Every sentence adds value, especially the actionable 'Branch on emptiness' and the sync threshold. It is thorough without being padded.

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 single-parameter lookup tool with an output schema already present, the description covers everything needed to call it correctly: what the parameter means, what success looks like, what failures look like, and how staleness can affect results. No critical guidance is missing.

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 0%, so the description must compensate. It explains that obj_id is 'The object's full ID,' adds the expected type, and provides a concrete example with a valid-looking ID. This gives the agent more semantics than the bare schema's 'Obj Id' title.

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 opens with a specific verb and resource: 'Look up any object (task, project, tag) by its ID.' This clearly distinguishes the tool from siblings like ticktick_get_all and ticktick_get_tasks_from_project because it is the generic ID-based lookup. The scope is explicit and actionable.

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 makes the primary use case clear: call this when you have a full ID and need that specific record. It also tells the agent to call ticktick_sync when a fresher result is needed, which is a useful usage condition. It stops short of explicitly naming alternatives or stating when not to use this tool, so it earns a 4 rather than a 5.

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