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

Annotations declare the safety profile (readOnlyHint=true, openWorldHint=false), so the description's job is to add return-value context, which it does: the score range, per-pattern flags, matched words, and reasons. It also notes it runs the same checker as a public tool, useful for trust. It stops short of stating determinism or rate limits.

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 tight sentences with no filler; the core action and output shape come first, and the external-tool reference is a compact trailing clause. Every sentence earns its place.

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 one-parameter read-only checker with no output schema, the description supplies what the agent otherwise couldn't know: the numeric scale and the structure of the returned findings. Nothing needed to invoke or interpret the tool is missing.

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?

There is a single parameter with 100% schema coverage ('The full post text'), so the schema already carries the semantics. The description mentions a 'post draft', which mildly reinforces that the full text is expected, but adds no format or length details. Baseline 3 is appropriate.

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?

States a specific verb (score) and resource (a LinkedIn post draft), plus the 0-100 scale and exactly what it detects: template patterns readers flag as AI-written. This is far more specific than a restated title, and no sibling tool overlaps with this scoring function.

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 makes clear this is for scoring a drafted LinkedIn post, which is an implied usage context, but it offers no explicit when-not guidance or named alternatives (the siblings are unrelated topic/guide tools). Adequate but leaves the agent to infer that the input must already be drafted text.

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