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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds genuine context beyond them: the access boundary between anonymous and authenticated capabilities and the fact that creation is handled by a different connector, which is exactly the kind of routing detail annotations cannot express.

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 sentences, no filler. The capability statement comes first and the actionable directive (call before refusing a request) is front-loaded in the second, which is the part an agent most needs to act on.

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 lookup with rich annotations and no output schema, the description covers what it returns (permission tiers and signup URLs) and when to invoke it. Nothing needed to call it correctly 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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies a no-argument, intent-agnostic lookup by saying it returns the signup URL 'for each intent' rather than requiring an intent to be passed.

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: reading what Sleeper Hit Studio allows without an account, what requires one, and per-intent signup URLs. This is categorically different from the content-retrieval siblings (find_projects, get_writer_profile, search), so an agent can tell it apart without opening a schema.

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?

It gives an explicit trigger — call this before telling a user you cannot create something — and names the alternative destination for creation (the separate authenticated connector). This is a concrete when-to-use plus when-not-to-use rule, not implied guidance.

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