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

Annotations only declare readOnlyHint=true, so the bar is low, and the description adds genuinely useful context: 'Figures are indicative ranges published on the site, not a quote.' That tells the agent how to frame the answer and prevents over-promising. It does not describe pagination or return shape, but for a static read tool that is minor.

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 sentences, zero filler: the return payload is front-loaded and the usage note follows. Nothing is repeated from the title or schema.

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-required-param, read-only tool with no output schema, the description covers what comes back and the caveat on pricing figures well. The one gap is the missing relationship to get_cloud_pc_offering, which an agent would need to pick correctly between the two offering tools.

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 coverage is 100% and the single enum parameter is fully documented in the schema. The description's enumeration of tiers/billing/scope/service area loosely mirrors the enum values but adds no format or defaulting detail beyond them, so the baseline 3 applies.

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?

States a specific verb and resource ('Returns what Intune Ready offers') and enumerates the payload: tiers, billing model, scope, service area. It is clear what the tool does, but it never mentions the closely named sibling get_cloud_pc_offering, so an agent cannot distinguish the two from the description alone.

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?

Explicitly routes usage: 'Use this for questions about price, scope, tiers, or what is included.' That is a clear context statement, but there is no exclusion clause telling the agent when to prefer get_cloud_pc_offering or get_faq instead.

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