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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's 'Read-only' is a restatement, but the added 'no hourly quota' and the instruction to follow saved personal_instructions are genuine behavioral context not in the annotations. It does not discuss error behavior or freshness/caching of the returned context, which is the main remaining gap.

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?

The directive 'Call this FIRST' is front-loaded, which is exactly right for a session-bootstrapping tool. The single long sentence stuffing five return groups into one string is dense but every clause carries information; only minor readability loss from the run-on structure.

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 output schema, the description carries the full burden of explaining return values, and it enumerates them (base_instructions, skills index fields, enablement, personal_instructions, feeds with their sub-fields, feed limits). For a zero-parameter read tool this is as complete as an agent needs.

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 and the description has nothing to disambiguate. It adds no spurious parameter guidance, which is correct.

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 resource — server context, base instructions, skills index, user settings, feeds — and states exactly what each returned section contains. It is clearly distinguishable from siblings like get_skill and get_usage because it explicitly delegates skill loading to get_skill.

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 unambiguous invocation rule: 'Call this FIRST in every session.' It also names the follow-up alternative ('load the one for the task with get_skill'), so the agent knows both when to call this and what to call next.

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