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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered by structured data. The description adds nothing beyond that — no note on what a sync job record contains, whether not-found is possible, or how the response is shaped. No contradiction with annotations.

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?

Brevity is not a virtue here: the same endpoint sentence appears twice in a row, which is pure waste, and what remains is an operation UUID plus a pointer to another tool. Only one of the three sentences carries any information.

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 nested-object, zero-described-parameter tool with no output schema, the description should explain the single-record retrieval semantics and the ID's meaning; instead it defers entirely to describe_operation. An agent must call a sibling tool to learn anything about the request shape.

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 description does not compensate. The ':id' path token faintly maps to params.id, but nothing explains what the ID identifies, and the nested 'query' object parameter is left entirely undocumented in both schema and prose.

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 is the raw route string 'GET /api/accounting-integration/sync-jobs/:id' repeated verbatim twice, which only restates the name and title. It never says in plain language that it retrieves a single sync job record by ID, and it does nothing to separate it from the sibling list tool get_accounting_integration_sync_jobs_dc723bca47df10fef58c8b23.

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 guidance, no prerequisites, and no mention of when the sibling list endpoint or describe_operation should be preferred. The only actionable hint is 'describe_operation provides native request schemas', which is a discovery pointer rather than usage guidance.

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