Memos overview

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety behavior is covered. The description adds value beyond them by disclosing the breadth of returned content (statistics, spaces, saved-view filters), which tells the agent what kind of side-effect-free aggregate call it is getting.

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?

One front-loaded clause ("Orientation in one call") followed by the content inventory and a one-sentence usage directive. No filler, no repetition of the title, and the highest-value information (what you get, when to call) leads.

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 compensates by enumerating the return content, which is precisely what an agent needs to decide whether this call supplies the context it wants. Nothing required to invoke it correctly is absent.

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 there is nothing for the description to disambiguate; baseline 4 applies. The schema is an empty object with 100% coverage, and no parameter claims in the description are missing or contradictory.

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 function (a single aggregate orientation call) and enumerates exactly what it returns: signed-in identity, instance/version, memo/task/tag statistics, recent activity, spaces, and saved views with filters. This is unmistakably distinct from the CRUD-oriented siblings (get_memo, search_memos, list_tags, etc.), which each target one resource.

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?

"Call this first when you need context" gives a clear, actionable when-to-use directive, which is strong for a zero-parameter bootstrap tool. It does not state any when-not condition or name an alternative, but there is no real alternative among the siblings for aggregate orientation, so the omission is minor.

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