Metis — Focus Brief

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

With no annotations, the description carries the full burden; it hints that this is a textual rendering of a surface, which is useful behavioral context. However, it does not explicitly state that the operation is read-only, nor does it describe side effects or prerequisites beyond the Desktop/dashboard contrast.

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 definition is short and front-loads the key content: saved, new, and open items. The second sentence adds context about the text form and Desktop, though the phrasing is slightly cryptic and could be clearer.

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?

Although an output schema exists and reduces the need to explain return values, the description leaves important gaps: it does not clarify the slug parameter, does not distinguish this brief from related focus tools, and does not state read-only behavior. For a tool with several focus-oriented siblings, this is notably incomplete.

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 sole parameter 'slug' has 0% schema description coverage, and the description never explains what the slug identifies or its expected format. 'One focus area' weakly implies the slug selects a focus area, but the description does not compensate for the missing schema documentation.

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 says the tool covers 'everything on one focus area' and enumerates saved/new/open content, but it lacks a precise verb and does not distinguish itself from siblings like preview_focus_lens or show_focus_areas. It conveys the general idea of a focused brief without fully pinning down the operation.

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?

The note 'for Claude Desktop, which has no dashboard' implies a usage context, but there is no explicit guidance on when to use this instead of preview_focus_lens, show_focus_areas, or update_focus_overview. Any guidance is left to inference.

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