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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly states the action is a read ('Read') and explicitly disclaims side effects ('No executable quote, payment or job is created'). This is strong transparency for a no-parameter tool, though it could add details about response format or data sources.

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 short sentences with no filler. The core action and resource are front-loaded, and the disclaimer about not creating anything follows naturally. Every sentence 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 parameterless read-only preview tool, the description is largely complete. It names what is read (scopes and cost policy) and what will not happen. It does not describe the exact output shape, but there is no output schema and the read scope is reasonably clear given the tool name.

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, so there is no parameter documentation burden. The description does not need to explain parameters, and the baseline of 4 applies because the description correctly orients the agent without schema-driven parameter semantics.

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 ('Read') and names a clear resource ('future hosted research scopes and cost policy'). It also explicitly states what the tool does NOT do ('No executable quote, payment or job is created'), which helps distinguish it from tools that actually create or execute work.

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 implies this is a preview/read-only tool and that no commitments are made, which is a usage signal. However, it does not explicitly mention when to choose this over sibling tools or state any exclusions or prerequisites. The guidance is present but mostly implicit.

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