discover_hub_tools

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

Describes the action as connecting to hub servers and retrieving tools, implying a read operation. However, with no annotations, it lacks information about side effects (e.g., caching, permissions) or state changes, which would be valuable for an agent.

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 includes some redundancy ('Connects to hub servers and retrieves their available tools' restates the first sentence). It is structured but could be more concise.

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 tool with one optional parameter and an output schema, the description covers the basics. However, it does not explain the relationship with sibling tools like 'list_hub_tools' or clarify what 'enabled servers' means.

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?

With 0% schema description coverage, the description fully explains the only parameter 'server_name', including its optional nature and behavior. This compensates for the schema's lack of descriptions.

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?

Clear verb ('discover') and resource ('tools from hub servers') indicate what the tool does. However, it does not differentiate from the sibling tool 'list_hub_tools', which may serve a similar purpose.

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 guidance on when to provide 'server_name' (to discover from a specific server) and when to omit it (discover from all enabled servers). But it does not explain when to use this tool over alternatives like 'list_hub_tools' or 'get_hub_tool_schema'.

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