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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds some context about the response shape (what Tabflows does with the tool, its features, and its page) but says nothing about not-found behavior, errors, or other edge cases.

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 a single front-loaded sentence: the key selection mechanism ('One integration by slug') comes first, followed by the content preview. Every word contributes, with no filler.

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 low-complexity read-only tool with one parameter and an output schema, the description is mostly sufficient: it tells the agent what to pass and what kind of data to expect. It does not address error cases, but the output schema and annotations cover much of the remaining context.

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 must compensate for documenting the slug parameter. It only says 'by slug,' which largely restates the parameter name and adds little beyond what the schema's pattern already implies; it does not explain how to obtain a valid slug or what the slug refers to beyond 'integration.'

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 identifies the resource as a single integration selected by slug and previews the returned content ('what Tabflows does with that tool, its features and its page'). It is clear enough to distinguish from sibling list_integrations, though it lacks an explicit verb beyond the tool name.

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?

The phrase 'One integration by slug' implies this is the tool to use when you already have a slug and need a single integration, as opposed to listing integrations. However, it never explicitly names an alternative or states when not to use it.

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