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

The annotations cover critical safety signals like readOnlyHint and destructiveHint. The description adds crucial behavioral context regarding the *content* retrieved (e.g., pricing, HTTP endpoints, docs), which is highly valuable for operational transparency.

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 definition is highly concise and front-loaded. It achieves maximum information density in a single, efficient sentence without any unnecessary filler.

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?

Given the tool is a simple, zero-parameter information provider, the description is maximally complete, providing a full mental model of what the agent can expect upon invocation.

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?

Since the tool has zero parameters, the baseline score is high. The description confirms that the tool operates as a simple information retrieval function requiring no user input.

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 is highly specific, clearly stating that the tool provides metadata regarding the service's functionality, pricing, and documentation links. This distinguishes it well from the sibling tools which focus on content (reading/preview).

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 establishes the tool's explicit context—general information about the platform. While it does not explicitly define 'when not to use it,' the clear scope of the information provided makes usage obvious for an AI agent.

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