get_hosted_mcp_urls

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

With no annotations provided, the description carries the full burden. It discloses the source (mcp.json), the OAuth requirement for hosted URLs, and the server's limitations (no implementation, no token acceptance, no proxying). This sets accurate expectations for the 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?

Three sentences, with the primary action front-loaded in the first sentence. Each sentence contributes either usage guidance or critical limitations with no redundancy.

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 zero-parameter tool with no output schema and no annotations, the description is complete: it explains what is returned, when to use it, and what it does not do. An agent can safely and correctly invoke the tool.

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 tool has zero parameters and the schema already makes this clear with 100% coverage. The description adds no parameter details, which is fine; a baseline of 4 is appropriate for a no-parameter tool.

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 uses a specific verb and resource: 'Return AdsAgent hosted HTTP MCP URLs from this repo's mcp.json.' This clearly states what the tool does and distinguishes it from sibling tools that operate on skills and readmes.

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?

It explicitly says 'Use this when a client needs the real Meta, Google Ads, or TikTok ads MCP endpoints,' and then clarifies what the docs server does not do (implement ads tools, accept tokens, proxy endpoints). This provides both a when-to-use and a when-not context.

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