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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description adds genuine scope context beyond that — the exact data window (12 trailing months, last 24 months) — but says nothing about error behavior for unresolved names or what max_rows caps.

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, content scope front-loaded and the example value appended. Every clause conveys callable information.

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?

With an output schema present, return values needn't be explained, and the description still usefully states the data scope and resolution behavior along with a sample input. Only the unexplained max_rows and no-match handling keep it from being fully 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?

Schema coverage is only 50%: area_concesion is documented and its 'close names are resolved' behavior restated in the description, plus a concrete example value. However, max_rows is unexplained in both schema and description, so the description only partly compensates for the coverage gap.

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+resource ('One concession area') and enumerates the exact profile contents (12-month production, YoY change, operators and shares, wells by type/state, top wells, last 24 months), so an agent can distinguish it from query_production or query_wells. It does not explicitly contrast with get_well/get_company, its closest siblings, so it stops short 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?

No when-to-use, when-not-to-use, or named alternative is given. The content list implies what you get back and the schema note about name resolution hints at usage, but an agent is left to infer that this is the entity-profile entry point versus resolve_entity or get_company.

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