List Meetings

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

The description adds behavioral context beyond the annotations: it states the return is a 'paginated JSON array of Meetings' and mentions pagination metadata. Annotations already declare readOnlyHint, destructiveHint, and idempotentHint, so the description's addition of pagination behavior is valuable.

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 concise (3 sentences) and front-loaded: first sentence states purpose, second gives usage guidance, third provides API context. Every sentence adds value without redundancy.

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?

While the description explains pagination and required parameters, it does not describe the return structure of a Meeting object. Since there is no output schema, the description should provide more detail about the response fields. However, it does include API endpoint and pagination metadata, which partially compensates.

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 baseline is 3. The description adds minimal meaning beyond the schema, only noting that page/per_page control pagination and that project_id is required. It does not elaborate on deleted_only or serializer_view, which are already well-documented in the schema.

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 'Returns a list of all Meetings for a specified Project' with a specific verb and resource. It distinguishes from sibling tools (create, show, update, delete) by mentioning 'list' and 'enumerate', making the list action unambiguous.

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 explicitly says 'Use this to enumerate Meetings when you need a paginated overview, to find IDs, or to filter by query parameters', providing clear guidance on when to use it. It does not explicitly mention when not to use it, but this is adequately covered by the context of paginated listing.

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