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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: the content is static, it is idempotent enough to call once per session, and it explicitly does not expose the chat system prompt, persona, or user data — a useful disclosure about what will and will not be 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?

The imperative "REQUIRED READING" is front-loaded, followed by scope, then contents, then timing, then exclusions — a sensible priority order. The single sentence groups four clauses and runs long, but each clause carries distinct information an agent needs.

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, closed-world info tool with no output schema, the description fully covers what it returns, when to call it, and what it withholds. Nothing an agent needs in order to call it correctly is missing.

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. The description correctly says nothing about inputs, which is right for a no-arg orientation endpoint, and its content summary substitutes for what a parameter list would normally convey.

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 ("Returns a static overview of what SkipCalls is") and enumerates the exact contents: product structure, tool-routing guidance, and editing rules. It is unmistakably distinct from every sibling tool in the list, none of which is a documentation/orientation endpoint.

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?

Explicit timing instruction: "Call this once at the start of a session before touching any other tool," plus "REQUIRED READING for any external assistant connecting over MCP." This is an unambiguous when-to-use directive with an implicit exclusion (once, not repeatedly).

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