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

The readOnlyHint annotation already establishes this is a safe read, so the description's job is lighter. It adds genuinely useful context not in the annotations: the `limit` parameter is gated behind premium plans, which affects whether a caller can request more than one joke. It still doesn't explain what happens on a free plan if `limit` is supplied, or any rate-limit behavior.

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, front-loaded with the purpose and then the constraint. Every clause carries information relevant to calling the tool; nothing is padding.

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-optional-parameter, no-output-schema tool, the description covers purpose and the premium gating. The one notable omission is the return shape: with `limit` > 1 there is no output schema, so whether the result is an array of joke strings or a concatenated blob is unspecified.

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 100%, and the schema already documents range (1-100), default (1), and 'Premium only.' The description restates the same premium gating and the 100-joke ceiling, adding emphasis but no new meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb and resource ('Returns one or more random dad jokes'), so the agent knows exactly what it produces. However, it never distinguishes itself from the many joke siblings (getJoke, getJokeOfTheDay, getChuckNorrisJoke, getRiddles), leaving the agent to infer the difference from the name 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?

Usage is implied by the name and purpose, but there is no explicit when-to-use guidance and no mention of the alternative joke tools in the sibling list. For a trivial random-content endpoint this is survivable, but the absence of routing guidance against getJoke/getJokeOfTheDay is a real gap.

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