desk_get_entity_timeline

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

No annotations are provided; description carries full burden. It states the operation is to get a timeline but does not disclose return format, pagination behavior, permissions, or what constitutes 'timeline/activity history'. Error recovery hints at behavior but insufficient.

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?

Description is structured with bolded sections, front-loaded with the main purpose. Each section (prerequisites, next steps, use cases, error recovery) provides unique value without redundancy.

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?

While schema describes parameters and description provides prerequisites/use cases, there is no mention of response structure, pagination behavior, or what timeline entries contain. No output schema to compensate. The tool is relatively straightforward but would benefit from explicit info about the 'limit'/'from' behavior and typical usage limits.

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 covers 100% of parameters with descriptions. The description adds context by specifying that required parameters come from desk_search_entities, which is not in the schema. This is additive value.

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?

Description explicitly states 'Get timeline/activity history for a specific Desk entity record,' which is a clear verb+resource+scope. It distinguishes from similar timeline tools (crm_get_timeline, people_get_timeline) by specifying Desk and entity record.

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?

Provides explicit prerequisites (Department ID, entity type, record ID from desk_search_entities) and next steps/use cases, giving clear context for when to use. Does not explicitly mention alternatives or exclusions.

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