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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered; the description adds nothing on top. It says nothing about pagination, result caps, ordering, or what the sync-job records contain — all relevant for a collection 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 short, but it wastes its entire length repeating the identical path string twice. That duplication displaces any substantive content rather than making the definition compact.

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?

For a collection endpoint with an opaque nested 'query' parameter, no output schema, and no annotations gaps to fall back on, the description should explain filtering/paging and result shape. The describe_operation pointer is the only genuinely useful element, leaving the definition materially incomplete.

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 single meaningful parameter ('query') is an untyped free-form object with additionalProperties {}, so the schema conveys no semantics at all. The description's only help is telling the agent to call describe_operation for native request schemas, which is a useful pointer but does not itself explain any accepted keys or values.

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 only restates the HTTP verb and path ('GET /api/accounting-integration/sync-jobs') twice, mirroring the title without added explanation. It never clarifies what a 'sync job' is or how this list endpoint differs from the sibling get_accounting_integration_sync_jobs_by_... endpoint, so an agent cannot disambiguate from the name alone.

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 statement of when to use this list endpoint versus the by-ID sibling, nor any precondition, pagination, or filtering context. The only routing hint is the pointer to describe_operation, which addresses schema lookup rather than tool selection.

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