contacts_discover

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

The description goes beyond the readOnlyHint annotation by revealing that operational contacts tools are hidden until discovered and enumerating all operation names. This adds valuable behavioral context about the discovery workflow, which is not available from the annotations alone.

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 efficient: it states the core purpose in the first sentence, gives a clear usage instruction, and then lists operations. The list is necessary content for a discovery tool and adds no wasted words.

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?

The tool is simple and the description covers everything needed: what it does, when to call it, and what operations are available. No output schema exists, but the enumeration of operations provides sufficient context about the expected output (the list of names).

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 already fully documents the single optional 'query' parameter with a clear description. The tool description adds no additional parameter-level semantics, but schema coverage is 100%, so 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 lists available contacts operations, using the specific verb 'list' and resource 'contacts operations'. It also distinguishes from sibling discovery tools by being contacts-specific and explains the hidden-tools mechanism, making the purpose unmistakable.

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 explicitly instructs 'call this first, then call the tool you need by name', providing clear when-to-use guidance. This is a definitive usage directive that positions the tool as the entry point for all contacts operations, and there is no ambiguity about its role.

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