docs_discover

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, covering safety. The description adds that the tool 'reveals its hidden tools' and must be called first, which is key behavioral context. Auth and rate limits are not covered, but with annotations that is acceptable.

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-loaded with purpose and sequence in two compact clauses. The trailing 'Ops:' list is long but informative and earns space by enumerating available hidden tools; there is no filler.

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 one optional parameter and no output schema, the description provides the essential call-first workflow and reveals that a catalog and hidden tools are returned. Nothing critical for invocation is missing, though it could clarify what 'Ops' refers to.

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% and the sole optional parameter 'query' is documented as 'Filter keyword'. The description does not mention the query parameter or add syntax/format details, so it adds no value beyond the schema. 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 and resource ('Discover docs') and describes output: 'lists the catalog and reveals its hidden tools'. The docs domain distinguishes it from sibling discover tools like drive_discover, though no sibling is named explicitly in the text.

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?

Provides explicit sequencing: 'call first, then call the tool by name.' This tells the agent when to use it (first) and what to do next. No when-not or alternative discovery tools are mentioned.

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