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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description's 'Read-only' is redundant with those, but 'no auth' is genuinely additional operational context. It adds little else (no rate limits, no format), so a 3 is fair.

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?

A single front-loaded sentence listing the content areas with no filler. It is efficient, though the compressed comma-list style is slightly dense.

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 zero-parameter, read-only info tool with no output schema, the description tells the agent enough: it is static reference content with no auth needed. The only real gap is not saying when to prefer it over the classifier-specific siblings.

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 takes zero parameters, so the baseline of 4 applies; there is no parameter semantics to get wrong. The description correctly implies a static, argument-free retrieval.

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 names the specific resource (Tuatara Decide) and enumerates exactly what it returns: product explanation, NEXUS plan allowances, limits, and benchmark evidence. This clearly distinguishes it from siblings like get_decide_classifier, list_decide_classifiers, and decide_predict, which deal with concrete classifiers/predictions rather than product docs.

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?

There is no explicit when-to-use guidance and no alternatives named. An agent must infer that this is the 'read the docs first' call before using decide_create_classifier or decide_predict; nothing states that, nor any exclusion.

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