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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: the permission model is READ and ANALYSE only, which tells the agent it cannot mutate RUTHVEN state, and it previews the categories of information returned.

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 with a colon-delimited inventory of contents — no filler or repetition. The nested list of four items makes it dense but readable; it could be marginally tightened but every clause carries information.

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?

There is no output schema, so the description must preview the return content, and it does so by enumerating the four sections an agent will receive. For a zero-parameter describe tool with full annotation coverage, that is close to complete; only the format/shape of the returned documentation is left unspecified.

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 and the schema is fully described, so there is nothing for the description to clarify about inputs. Baseline for a no-parameter tool is 4; no param-specific claims are needed or missing.

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 a concrete deliverable — a self-description of RUTHVEN covering verification states, permission model, asset types, and JSON API endpoints — so the agent knows this is the onboarding/meta tool rather than a data fetch. It doesn't explicitly contrast itself with the get_/verify_/ask_ siblings, but the enumerated scope is specific enough to separate it from them.

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?

Usage is only implied: an agent reading 'what RUTHVEN is and what an agent may do with it' can infer this is the orientation call before using ruthven_verify_claim or ruthven_get_asset. No explicit when-to-use, prerequisites, or named alternatives are given, so the guidance remains inferential rather than stated.

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