get_session_brief

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

Annotations already declare readOnlyHint=true, and the description adds the specific data composition (expertise profile, conversations, stats) and efficiency hint. No contradictions. The description enhances understanding beyond annotations by detailing what the 'full context' entails.

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?

Two sentences, no waste. The key information (purpose, composition, usage context) is front-loaded and clearly structured. Every sentence serves a purpose.

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?

Given zero parameters and the presence of an output schema, the description sufficiently explains what the tool returns (expertise profile, conversations, stats) and when to use it (start of session). It's complete for the tool's complexity and context.

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?

There are no parameters (schema with empty properties). Schema coverage is 100%. The description doesn't need to add parameter info; it focuses on output and usage, which is appropriate. No additional semantics needed.

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 clearly states the tool's purpose: 'One-shot session bootstrap' that combines specific data (expertise profile, last 5 AI conversations, corpus stats) into a single JSON object. It distinguishes from siblings by emphasizing it's a consolidated one-shot call vs. multiple round-trips.

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?

Explicitly says 'Call this at the start of a session to load full context without multiple round-trips.' This provides clear when-to-use context and implies alternatives (multiple round-trips via other tools). No explicit when-not, but the guidance is strong.

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