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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description adds nothing beyond them. It doesn't mention pagination, date-range filtering, result ordering, or authorization requirements for a sync-history read.

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?

It is short, but the path is printed twice verbatim, so the sentences are boilerplate rather than front-loaded information. Nothing in it earns repeated space.

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?

With no output schema, zero parameter documentation, and nested free-form objects, the definition leaves an agent unable to construct a valid call without a round-trip to describe_operation. For a read endpoint with two opaque parameters, this is under-specified.

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 the two parameters ('query' as a free-form object, 'params' with no properties) are completely undocumented. The description's only help is deferring to describe_operation, which does not explain what query keys are valid or how filtering works.

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 restates the tool name/path twice ('GET /api/sitefolio/sync-history') and adds an operation ID, which is tautological rather than explanatory. It never says what a sync history contains or how it differs from siblings like get_integrations_by_id_sync_logs or get_import_history.

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 when-to-use or when-not-to-use guidance is given. The only actionable hint is 'describe_operation provides native request schemas', which points to a companion tool but doesn't define selection criteria against the many other history/log endpoints.

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