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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds topical scope but says nothing about the shape of what comes back (a doc page, structured text, links), which is the only behavioral detail still missing.

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, with the topic list and the imperative usage cue both up front. The topic list is slightly enumerative rather than prioritized, but it earns its space.

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 informational tool with no output schema, the description supplies enough: what subjects it covers and when to reach for it first. Only a hint about the return format would improve it.

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 there is nothing for the description to disambiguate; the baseline for a no-arg tool is 4. The description correctly implies a parameterless 'fetch the overview' call.

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 tells the agent this is the conceptual/onboarding resource for the Rightis registry, enumerating the topics it covers (public lookup, partner key, usage logging, persona policy, machine-readable signals). That clearly separates it from the data-returning siblings rights_lookup and rights_search, though it never states a crisp verb+resource like 'returns documentation'.

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 it first when you are unsure how to use the registry.' That is clear when-to-use guidance. It stops short of saying when NOT to call it or naming rights_lookup/rights_search as the alternatives for actual lookups.

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