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

With no annotations provided, the description carries the burden of behavioral disclosure. It does this well by enumerating what the page returns: definition, explanatory sections, FAQ, and related terms. It also implies a read-only lookup and provides slug discovery guidance, though it does not describe invalid-slug behavior.

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 contain all essential information with no filler. The main purpose and output structure are front-loaded, followed by practical examples and slug-discovery guidance. 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 single-parameter lookup tool with no output schema, the description is complete enough: it states what the response contains, gives examples, and explains how to obtain valid inputs. Nothing an agent needs to call this tool correctly is missing.

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 schema already fully documents the slug parameter, so the baseline is 3. The description adds value beyond the schema by giving multiple concrete example slugs and pointing to a discovery mechanism for obtaining valid slugs, making the parameter's expected format and provenance clearer.

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 states the action ('Get a full ... definition page'), the resource (Buckhead Energy Oil & Gas Encyclopedia), and the key identifier (slug). It differentiates itself from the data-focused sibling tools by explicitly scoping to encyclopedia concept definitions and giving representative domain examples.

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 gives clear context: use this for encyclopedia definitions of mineral-rights / oil & gas concepts. It also tells the agent how to discover valid slugs via buckhead://encyclopedia. It does not explicitly say when not to use it, but the sibling set makes the encyclopedia vs. data-tool distinction obvious.

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