list-meeting-attendance-reports

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds no behavioral nuance—such as report scope, permission requirements, or truncation behavior—beyond what annotations and schema already provide. There is no contradiction.

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 a single, front-loaded sentence with no wasted words. It clearly states the verb and resource in the fewest possible characters.

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 output schema and a nearly identical sibling tool, the description is too thin. It does not explain what an attendance report contains, how meetingId is obtained, or how these reports differ from list-meeting-attendance-records. Pagination details live in the schema, but the missing selection and return context makes this less than minimally complete.

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 input schema covers 100% of parameters, and cursor and maxItems have detailed, actionable descriptions. The tool description itself adds no parameter meaning, but the high schema coverage keeps this at the baseline. The meetingId schema description is weak, but the description does not compensate for it.

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 names the operation ('List') and the resource ('attendance reports') scoped to an online meeting, so an agent can tell what the tool does. However, it does not differentiate this from the near-identical sibling list-meeting-attendance-records, stopping just short of a 5.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of alternatives such as list-meeting-attendance-records. The intended usage is only implied by the tool name and the phrase 'of an online meeting', not explicitly stated.

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