Show Meeting

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the description does not need to repeat safety traits. It adds context about the API endpoint and return format (JSON object), but does not disclose behaviors like error handling, authentication requirements, or rate limits. This is adequate given the annotations, but not extra informative.

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 three sentences, each serving a clear purpose: stating the function, specifying usage, and providing technical details. It is concise and well-structured with no redundant information.

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?

The tool is a simple retrieval with four parameters, all documented in the schema. The description covers the main purpose and required parameters but omits optional pagination parameters (page, per_page) context. Given the schema covers these and there is no output schema, the description is mostly complete but could briefly mention pagination.

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% with all parameters described. The description adds the URL path template and highlights required parameters (project_id, id), but does not provide additional semantics beyond the schema. Since the schema already describes each parameter adequately, the description adds minimal extra value.

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 it returns detailed information about a Meeting in a specified Project using identifiers. However, it uses 'Meetings' (plural) inconsistently with the tool name, and could specify the exact data fields returned, which would further differentiate it from sibling tools like show_meeting_v1_0.

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 says 'Use this to fetch the full details of a specific Meetings by its identifier.' but does not provide guidance on when to use this tool over alternative show or list tools, nor does it mention prerequisites like project access or required permissions. This omission reduces its utility for an AI agent deciding between tools.

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