Get Tracked Updates

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

With no annotations, the description minimally states it is a read operation returning recent changes. It does not disclose pagination behavior, data freshness, or any side effects. Acceptable for a read tool but lacks depth.

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?

Single sentence front-loading the operation and purpose. 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?

Given the output schema exists, return values are covered. However, the tool has 3 undocumented parameters and no behavioral details (e.g., is course filtering exact or partial?). The description is adequate for a simple read tool but incomplete for effective use.

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% and description does not explain the three parameters (limit, course, entity_type). The description adds no value beyond the schema, failing to clarify default values or acceptable formats.

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 clearly states it reads stored tracking history and returns recent changes. The verb 'Read' and resource 'stored Ninova tracking history' are specific. Distinguishes from sibling tools like crawl_course or snapshot_page which perform different actions.

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?

No guidance on when to use this tool versus alternatives like crawl_course, diff_snapshot, or sync_all_courses. The description does not mention prerequisites, filtering conditions, or contexts where get_updates is preferred.

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