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

With zero annotations and no output schema, the description carries the full burden of behavioral disclosure, and it discloses nothing. It doesn't state whether the tool is a read-only check, what it evaluates, whether it can error, or what the response shape looks like. There is no behavioral information of any kind.

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 short, but this is under-specification, not conciseness. The repetitive 'Is Cullen: Is Cullen' wastes the reader's attention by delivering zero information in two renderings of the same phrase.

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?

The tool has no annotations, no output schema, a tautological description, and lives among thousands of similarly-named predicates. An agent has literally nothing to reason with — it cannot determine purpose, invocation requirements, or expected output. This is completely inadequate.

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?

The tool has zero parameters, so per the rubric the baseline is 4 and the description is not expected to document parameter semantics. However, the empty schema combined with a tautological description leaves ambiguity about what entity is being checked for 'Cullen-ness' — the schema likely should define an input.

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 Cullen: Is Cullen' is a pure tautology that restates the tool name without adding any meaning. It never states what a 'Cullen' number is, what operation is performed, or what the tool returns. An agent browsing 2000+ sibling tools would be completely unable to distinguish this from the many other 'is-*' predicates.

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 is provided about when to invoke this tool versus any alternative. The description gives no context about Cullen numbers, what input conditions trigger a true result, or how this differs from sibling predicates like is-abundant or is-prime.

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