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

Goes well beyond the readOnlyHint annotation: it discloses the org-wide scope ('Issues and to-dos are the organization's, not filtered to the meeting's team'), that fields are trimmed to agenda needs, that omitted items are only represented as counts, and that include_closed returns the 100 most recent resolved items. These are non-obvious behavioral traits an agent could not infer from annotations or schema.

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?

Front-loaded with the return contents and the scope caveat before the optional parameter and the use case. It is dense but every clause carries substantive information; a slightly tighter structure (separating return shape from scope caveat) would earn a 5.

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?

There is no output schema, so the description must characterize the response — and it does so thoroughly: the component objects, field trimming, included statuses, and the counts standing in for excluded records. An agent has enough to decide to call it and to interpret the result.

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?

At 50% schema coverage, the description must compensate: it does explain include_closed's effect ('also get recently resolved issues and done to-dos'), adding nuance beyond the schema's '100 most recent' note. However, meeting_id is entirely undocumented in both schema and description beyond the implied 'one meeting', so the coverage gap is only partially closed. Baseline 3.

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?

Specific verb and resource ('Get one meeting's agenda') followed by an explicit inventory of what the payload contains: the meeting, scorecard snapshot with KPI values, rocks snapshot, open issues/to-dos, plus counts of excluded items. This is clearly distinguishable from sibling list_meetings (enumeration) and get_meeting_transcript (transcript content).

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 closing sentence 'Use to prep, render or summarize a meeting' gives a clear use context, and the include_closed clause states a concrete conditional. It stops short of naming alternatives or exclusions (e.g. when to prefer list_meetings or get_meeting_transcript), so it is clear but not fully routing.

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