team_briefing

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does an admirable job explaining the compact projection behavior, clarifying that compact means 'trimmed, NOT missing fields', describing how event payloads and pending tasks are projected, and even citing a measured character count on a real team. This goes well beyond a typical description.

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 description is somewhat long (multiple paragraphs) but front-loads the core purpose in the first sentence, then layers projection details and a measured-size data point that are genuinely useful for an agent deciding how to consume the response. The compact-vs-trimmed clarification earns its place though it adds length.

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?

This is a moderately complex tool with 5 parameters, an output schema, and no annotations. The description covers the response structure, the compact projection semantics, and references the related agent_list convention. It explains what the caller will receive well. Minor gap: no explicit statement about what 'action suggestions' means or costs/limits of the full briefing, but the measured-size hint partially addresses this.

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?

Schema description coverage is 100%, so the schema already documents all 5 parameters thoroughly (limit, fields, team_id, include_offline, offline_preview). The description adds context about the 'compact projection' concept referenced in the fields and limit parameters, reinforcing what the schema says. Baseline 3 is appropriate since the schema does the heavy lifting.

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 provides a 'team panoramic briefing' covering team info, member status, events, meetings, tasks, and suggestions. The verb 'Get' plus the resource 'team briefing' is specific, though it doesn't explicitly distinguish from siblings like team_status or team_list. The mention of 'one call' adds context.

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 description implies this is for understanding 'full team status in one call' and references the sibling agent_list convention, but provides no explicit when-to-use vs alternatives guidance. It doesn't say when NOT to use this and prefer team_status, team_list, or agent_list. Usage context is implied rather than stated.

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