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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered externally. The description adds real value by disclosing the content scope — including that it documents 'what is deliberately not available here,' which is a genuine transparency signal about limits. It stops short of saying when data was last refreshed or how to interpret the payload.

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 no filler, and the content topics are ordered from identity outward. It is a fragment rather than a full sentence, and the opening 'What INDICIA DESK is' partly restates the title, but nothing is wasted.

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 documentation tool with an output schema (so return values need no explanation) and full annotation coverage, the description is close to sufficient. The one missing element is explicit invocation guidance — telling the agent to call it at session start.

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; there is no parameter semantics to explain and the description correctly introduces none.

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 the resource precisely (INDICIA DESK / this server) and enumerates the exact content it returns: identity, per-tool return values, data freshness, deliberate omissions, and plans. It is clearly distinct from the domain siblings (decision_journal, expiry_record, hypothesis_ledger, market_state), though it never states that distinction explicitly.

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 must infer that this is a first-call orientation tool. There is no explicit 'call this before using the other tools' instruction, no when-not-to-use guidance, and no mention of the siblings as alternatives.

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