list_history_since

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description does not need to repeat those. However, it adds no extra behavioral context such as pagination limits, authentication requirements, or how parameters affect results. It is essentially just a label and endpoint.

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 brief, but brevity is not conciseness when it omits essential information. The structure (one sentence and a bare list of args) is minimal and does not earn its place beyond restating schema field names. It could be trimmed further without loss.

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 4 optional parameters, no schema descriptions, and an output schema that is not referenced, the description is severely incomplete. It does not explain the 'since' semantics, valid event types, or what the include flags control. An agent cannot call this tool correctly with the information provided.

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 description coverage is 0%, so the description must compensate by explaining parameters. It merely lists the parameter names without any descriptions or examples. The agent cannot infer what 'date', 'event_type', 'include_series', or 'include_episode' mean or how to format them.

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 states 'Read History' and gives the endpoint, which is a clear verb+resource. However, it does not explain what 'since' means or what differentiates it from sibling tools like list_history and list_history_series. It is not a tautology but lacks specificity.

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 is provided on when to use this tool versus alternatives. There is no mention of filtering by date, event type, or when to prefer list_history or list_history_series. The agent is left without any routing information.

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