calendar_discover

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

Annotations already mark it read-only, idempotent, and non-destructive. The description adds that it reveals hidden tools and must be called before invoking them, which is useful behavioral context, but it omits return format, pagination, or auth details.

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 purpose and usage in the first sentence, then lists available operations. The enumeration is long but informative for a discovery tool; the '+1 more' phrasing is slightly messy but not severely wasteful.

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, it explains that it returns a catalog of hidden tools and how to invoke them. It does not cover the query parameter behavior or relationship to sibling discovery tools, but core invocation is addressed.

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% and the single query parameter is already documented in the schema as 'Filter keyword'. The description does not mention the query filter or add meaning beyond the schema, so the baseline 3 applies.

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 'Discover' and resource 'calendar', and clarifies it lists the catalog and reveals hidden tools. It does not explicitly differentiate from sibling discovery tools like discover_all or google_api_search, though the calendar scope is clear.

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?

Explicitly says 'call first, then call the tool by name', giving clear ordering context. It does not mention when not to use it or name an alternative such as discover_all, so it is not a full 5.

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