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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that source links are audience-specific, but it does not disclose what the response contains or how behavior changes when audience is omitted.

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 description is a single sentence with no filler and front-loads the resource type. It is appropriately short, though the brevity sacrifices specificity.

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?

The tool has no output schema and one partially described optional parameter, so the description needs to explain what is returned and what audience controls. It only says 'source links' vaguely, and it does not contrast with similar sibling tools. The simplicity of the tool prevents a score of 1, but the gaps are material.

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%, so the description must compensate for the undocumented audience parameter. It only echoes the word 'audience-specific' and does not explain the enum values, optionality, or behavior when the parameter is omitted.

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 names the resource ('mineral management and operator back-office services') and an audience qualifier, but it is a noun phrase rather than an explicit verb+resource statement. It does not clearly state that the tool retrieves or lists services, nor does it distinguish itself from the sibling find_relevant_service.

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?

There is no guidance about when to use this tool versus alternatives such as find_relevant_service or about_valor. The audience parameter hints at possible use cases, but the description never states an explicit condition or exclusion.

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