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

With no annotations, the description carries the full burden. It does useful work by disclosing the identity scoping ('the person this TeamMeet connector belongs to') and the ordering behavior ('Open ones first'), which implies a read operation. But it never confirms read-only status, says nothing about result volume, pagination, or whether the default set excludes finished items — the last point is left to the 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?

Three short clauses, purpose front-loaded, with the sibling routing at the end where it belongs. The em-dash aside about the connector's owner is slightly convoluted but earns its place by establishing the scope of 'you'.

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, and the description compensates well by enumerating the fields each task carries (requester, request, call, status). For a one-optional-boolean list tool this is close to complete; only pagination/volume expectations are unaddressed.

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 coverage is 100% and the single `all` parameter is already documented as 'Include finished and declined ones too,' so the schema does the heavy lifting. 'Open ones first' adds ordering flavor but arguably blurs whether open-only is a filter or just a sort, which is exactly what the `all` flag controls.

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 identifies the resource precisely — action items handed to the connector's owner — and enumerates what each carries (who asked, what they asked for, which call, current status), which clearly separates it from siblings like get_transcript or list_meetings. It loses a point because the verb is never stated plainly; 'what your calls have handed to you ... to do' requires the agent to infer 'list my tasks'.

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?

'Open ones first' signals the default ordering/priority, and 'Use get_task for the whole of one' explicitly routes the agent to the sibling for detail. What's missing is any statement of when NOT to use it (e.g. for tasks belonging to other people, or for tasks unrelated to calls).

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