meet_discover

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a key behavioral trait: operational meet tools are hidden until discovered, requiring this tool to expose them. This goes beyond the annotations and explains the discovery mechanics.

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 front-loaded with the main action and then provides a concise explanatory sentence. The long list of operations is a single sentence but provides valuable reference data. No wasted words, though the list is necessarily lengthy.

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?

For a discovery tool with no output schema, the description explains the purpose and the first-step requirement. It lists all operations so the agent knows what to expect. It could mention the query parameter's role in filtering, but the schema covers that, making the description adequately complete for its complexity.

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 has one parameter (query) with 100% description coverage. The tool description does not add any additional meaning to the parameter, so the schema carries the full weight. Baseline 3 is appropriate.

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 tool's verb and resource: "List the available meet operations." It distinguishes itself from sibling discover tools by explicitly naming the meet scope and enumerating the specific operations it returns, making its purpose 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 provides explicit usage guidance: "call this first, then call the tool you need by name." It explains that operational meet tools are hidden until discovered, establishing a clear prerequisite. However, it does not explicitly mention when not to use this tool or name alternatives, though the sibling list implies service-specific discover tools.

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