List timeline notes

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond restating the HTTP method and path — no mention of default page size, ordering, whether results are capped at 500, or what happens when no filters are supplied.

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?

One short, front-loaded sentence with zero filler, so nothing is wasteful. However, this is terseness by omission rather than disciplined conciseness — the definition is undersized for a five-parameter filtered list.

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?

No output schema exists, so the description should carry more of the burden, yet it says nothing about return shape, ordering, pagination, or filter semantics. For a listing tool with five undocumented optional parameters, an agent cannot determine correct invocation from this definition alone.

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% and five parameters (to, from, limit, clientId, campaignId) are completely undocumented. The description's only parameter-adjacent content is the endpoint path, which explains nothing about date-range boundaries, pagination via limit, or what clientId/campaignId scope to.

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?

States a specific verb ("List") and resource ("timeline notes") plus the backing endpoint GET /v1/notes, which clearly separates it from the notes_create/update/delete siblings. It lacks any explicit sibling reference, but the read-only framing is unambiguous.

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?

There is no when-to-use guidance at all — no statement of what a timeline note is in this product, when an agent should list them versus using reports/audit/actions tooling, or how the date filters should be chosen. Usage is only inferable from the verb "List".

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