security_controlled_get

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

The description asserts 'No state-changing requests', i.e. a read-only operation, while the annotations declare readOnlyHint=false. That is a direct inconsistency. Beyond the contradiction, the description does add genuinely useful behavior (pinned DNS, no redirects, bounded single request), but the read-only claim conflicts with the structured hint.

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?

Two terse sentences, front-loaded with the operation and then the safety constraints; no filler. It is arguably over-terse, but every clause earns its place.

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 5-parameter, security-sensitive network tool with no output schema and 0% schema description coverage, the description should explain the remaining parameters and the account/auth model. It covers behavioral guardrails reasonably but leaves project, environment, and authorization unexplained and contradicts the read-only annotation.

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 description coverage is 0% across 5 parameters, so the description carries the full burden. It only loosely gestures at two of them ('authorized origin' -> url, 'controlled account' -> account) and says nothing about project, environment, or authorization, nor about required URI/pattern formats.

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 states a concrete verb+resource: a single bounded HTTP GET to an authorized origin under a controlled account. An agent can tell this is a network-fetch tool rather than one of the read_/store_/task_ siblings, though it never names a sibling or explicitly scopes itself against them.

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?

Constraints imply usage ('exact authorized origin', 'controlled account', 'no state-changing requests') but there is no explicit when-to-use/when-not or alternative tool named. The agent must infer that this is for safe, tightly scoped fetches rather than general HTTP access.

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