offerings

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

With no annotations provided, the description bears the full disclosure burden. It does state the read-only nature explicitly, which is the most safety-relevant trait. But it says nothing about return format, response size, pagination, or performance for what could be a large coverage matrix, leaving behavioral expectations incomplete.

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 short sentences with the core purpose front-loaded in the first sentence. Every clause earns its place, and the read-only plus use-case framing is efficient. Minor redundancy between 'coverage matrix' and listing the fields, but no meaningful waste.

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 tool with no output schema, the description's job is largely to convey what is returned and why it matters. It covers the return content and the entitlement use case adequately. It could mention the response shape, but given the zero-parameter simplicity, the description is near-complete.

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?

With 0 parameters and additionalProperties=false, the schema coverage is 100% and there is nothing for the description to elaborate on parameter meaning. Per baseline, a 0-param tool is scored 4; the description adds value by explaining what the returned data conceptually represents (supplier families, routes, entitlement, write-gating).

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 clearly identifies the resource (offerings) and the specific content: 'every supplier family, its exposed routes, entitlement state, and write-gating.' It reads as a listing/coverage tool distinct from sibling tools like domains_dns and portfolio_health, which target different domains. The verb is implicit rather than stated ('matrix' implies get/list), which keeps it a half-step shy of a 5.

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?

'Useful to see what this tenant is entitled to' gives a broad usage context, and the read-only emphasis implies it is safe for inspection purposes. However, there is no explicit when-to-use vs. when-not-to guidance, and no alternative sibling tool is named, so an agent must infer routing from the domain keywords alone.

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