meetings_get

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Get details' implies a read operation, it doesn't specify whether this requires authentication, what permissions are needed, whether rate limits apply, what happens with invalid meeting IDs, or what format/details are returned. For a tool with zero annotation coverage, this is insufficient.

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 perfectly concise at 6 words, front-loading the core purpose with zero wasted words. Every word earns its place, making it immediately scannable and understandable.

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?

Given 3 parameters with 0% schema coverage, no annotations, and no output schema, the description is woefully incomplete. It doesn't explain parameter usage, behavioral constraints, return format, or differentiation from sibling tools. For a tool with this complexity and lack of structured documentation, the description should do much more.

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?

With 0% schema description coverage and 3 parameters (meetingId, properties, associations), the description provides no parameter information whatsoever. It doesn't explain what 'properties' or 'associations' mean, what values they accept, or how they affect the returned details. The description fails to compensate for the complete lack of schema documentation.

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 the verb ('Get') and resource ('details of a specific meeting'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'meetings_list' or 'meetings_search' that also retrieve meeting information, which prevents a perfect score.

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 provides no guidance on when to use this tool versus alternatives. With sibling tools like 'meetings_list' (for multiple meetings) and 'meetings_search' (for filtered searches), the agent receives no help in choosing between them. The description only states what the tool does, not when it's appropriate.

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