meet_discover

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

Annotations already declare readOnlyHint/idempotentHint true and destructiveHint false, so safety is covered. The description adds genuine behavioral context beyond them: that it enumerates a catalog plus hidden tools, and that it is the prerequisite entry point for named tool calls.

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?

Front-loads the purpose before the op enumeration, and every clause carries information. The long semicolon-delimited ops list is useful but slightly dense.

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 adequately explains what it returns (catalog + hidden tools) and the follow-up workflow. It could note polling/refresh behavior or relationship to discover_reset, but nothing critical is missing.

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?

Only one parameter (query) with 100% schema description coverage, so the schema already documents it as a 'filter keyword.' The description adds no further semantics about its matching or format, which is the expected baseline when the schema fully covers the parameter.

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?

States a specific verb and scoped resource: 'Discover meet: lists the catalog and reveals its hidden tools.' The 'meet' scoping distinguishes it from gmail_discover/drive_discover siblings by resource, though it never contrasts with discover_all or discover_reset.

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?

Gives clear sequencing guidance ('call first, then call the tool by name'), telling the agent this must precede invocation of the enumerated ops. It stops short of explaining when to prefer it over discover_all or other parallel discover tools.

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