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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered without the description. The description adds nothing beyond that — no statement of what is retrieved, whether it 404s for unknown ids, or auth prerequisites. The only added value is the pointer to describe_operation for schemas.

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?

Short, but the first two sentences are identical duplicates that carry zero incremental information. The only substantive content — the operation ID and the describe_operation pointer — is buried after the repetition.

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?

There is no output schema, so the description should convey at least what shape of data comes back; it does not. With a nested `params` object, an untyped `query` object, and zero schema descriptions, the definition leaves an agent unable to call this confidently beyond pasting an id.

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%, so the description is expected to compensate, and it largely does not. The ':id' in the repeated path hints that id is a path parameter, but the free-form `query` object parameter is never mentioned and neither is any format or constraint for the id.

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 literally the endpoint path repeated twice — 'GET /api/integrations/:id. GET /api/integrations/:id.' — which restates the title without saying what an integration is, what fields it returns, or how it differs from the sibling list tool get_integrations_b405361088b53adc4ec4247b or get_integrations_by_id_sync_logs. A reader can infer 'fetch one integration by id,' but only from the raw path, not from explanatory prose.

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 guidance on when to call this versus the sibling integrations-list tool or the sync-logs-by-id tool. The only routing hint is 'describe_operation provides native request schemas,' which points at a metadata tool rather than explaining use conditions.

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