Show ToolHub capabilities

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered. The description adds only the words 'versioned' and 'public', contributing essentially no behavioral context beyond the structured fields.

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?

A single sentence with no wasted words and the core claim front-loaded. It is efficient, though bordering on under-specification rather than true comprehensiveness.

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?

Output schema richness means return values need not be described, and annotations cover the safety profile. Still, for a discovery/meta tool the description is thin enough that an agent cannot tell what the contract actually contains or when this is the preferred call, leaving a real gap.

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?

This tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description is needed to disambiguate inputs.

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 verb 'Return' and resource 'ToolHub execution contract' are specific, and the title reinforces it as a capabilities/self-description tool. However, 'versioned public execution contract' is opaque jargon that does not plainly convey what an agent actually gets back, and it draws no line against siblings like toolhub.ping or toolhub.request_status.

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?

There is no indication of when to call this versus toolhub.ping, toolhub.audit_recent, or toolhub.request_status. The description states what it returns but gives no trigger condition, prerequisites, or exclusion guidance.

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