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

Annotations already establish readOnly/idempotent/non-destructive, so the description's added value is freshness and cost semantics: 'Generated nightly and on session disconnect' tells the agent the result may be stale, and '~500 tokens' flags it as cheap. Return shape and any staleness guarantees are left implicit.

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 payload description comes first, then the usage rule with its alternative. Every clause carries information the agent needs, including the token budget and generation cadence.

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 parameters and no output schema, the description must fully characterize the return value, and it largely does (bio content, ~500 tokens, freshness cadence) and names the fallback tool. Minor gaps remain around whether the seed can be absent for a new tenant or how stale it can be.

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 schema makes no semantic demands and the description has nothing to disambiguate. Baseline of 4 applies; the description correctly adds nothing extraneous about inputs.

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?

States a specific verb and resource ('Return the pre-computed session seed'), then defines the artifact concretely ('a compact first-person bio (~500 tokens)'). It explicitly positions itself against a named sibling (load_context), so an agent can distinguish the two without opening either 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?

Gives a clear selection condition ('when you just need orientation') and names the alternative tool (load_context) as the heavyweight option. It does not spell out explicit exclusions or prerequisites, but the tradeoff implies when not to reach for it.

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