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's only added behavioral signal is 'Same opening as get_post', which vaguely hints at a shared response shape but is too cryptic to rely on, and nothing is said about error behavior for unknown ids.

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?

Two short sentences with the core scope front-loaded and no filler. The second sentence is cryptic rather than verbose, so brevity is not the issue — clarity of that clause is.

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 single-parameter read tool with full annotation coverage and full schema coverage, the essentials are technically present. But with four siblings in a similar fetch/search space, the description lacks the differentiation and return-shape clarity needed to route an agent confidently.

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 coverage is 100% and the id parameter is described as 'Article slug from search'. The description repeats that same meaning ('by the id from search') without adding format, slug-vs-numeric, or validation details, so baseline 3 applies.

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 verb 'fetch' and resource 'one article by the id' are stated, and the id provenance ('from search') is clear. However, 'Connector-style' is undefined jargon and 'Same opening as get_post' doesn't establish how this differs from the get_post sibling — an agent can't tell which one to pick from purpose 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?

The description implies a workflow (id comes from search) but never states when to use this tool versus get_post, search_posts, or search. 'Same opening as get_post' gestures at a relationship without explaining the selection condition, leaving the core routing decision to inference.

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