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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds a valuable operational detail: the tool cannot be called with just the public link; it requires owner OAuth or guest token. This goes beyond the annotations without contradicting them, giving an agent a concrete precondition for successful invocation.

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 a single sentence with no filler, and it immediately conveys the most important constraint. It is appropriately brief, though it starts with a behavioral note rather than the purpose, which may reduce front-loading of what the tool actually does.

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?

With no output schema and no information about return values, the description is incomplete for an agent deciding what to expect. It doesn't mention what 'conversion' or 'state' means operationally, how to interpret the result, or any failure modes beyond the auth note. For a status-checking tool, this is a significant gap.

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 0%, so the description must compensate for both parameters. It clarifies that guest_token is a form of auth and that the public link alone won't work, but it says nothing about catalogue_id or how the two interact. The title hints at catalogue_id's role, but the description leaves a large semantic gap for a required parameter.

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 title clearly states the tool checks catalogue conversion and state, but the description itself only mentions an authentication requirement and doesn't restate or refine the purpose. It also doesn't distinguish this tool from the similarly named sibling foliade_catalogue_stats, leaving ambiguity about which one to choose.

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 provides a usage constraint: private state requires owner OAuth or guest token, and the public link alone is insufficient. This implies when auth is needed but gives no guidance on when to prefer this tool over alternatives like foliade_catalogue_stats or foliade_get_catalogue_settings, so usage context is only partially covered.

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