get_changes

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

No contradiction with annotations (readOnlyHint, idempotentHint). Adds behavioral details: returns DCPI market movers, new facilities, deals, news, and portfolio block for keyed callers with saved sites. Describes caching and reusing generated_at.

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?

Front-loaded with purpose and key behavior. Dense but well-organized. Could be slightly shorter but every sentence adds value.

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 no output schema, description adequately explains return types: market movers, facilities, deals, news, and customized portfolio block. Covers delta sync mechanics. Fairly complete for a read-only, idempotent tool.

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 100% already documents both parameters. Description adds value by explaining since parameter in detail: supports ISO-8601, '24h', '7d', default 24h. No extra for limit but schema is sufficient.

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 clearly states 'Incremental sync — what changed in DC Hub since a timestamp' with specific verb 'get changes' and resource 'DC Hub'. It distinguishes from sibling tools like get_facility or get_news by focusing on delta updates.

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 usage: 'so an agent pulls only the delta instead of re-fetching everything' and instructs to pass since parameter, cache generated_at. Includes example 'get_changes since=7d'. Lacks explicit when-not-to-use but clearly conveys primary use case.

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