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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral context about the depth and provenance of the response — estimates 'as the release printed them', the effective date and reporting code, named qualified persons tied to their newest release, and the 6ix.com link per release. It does not cover failure behavior (unknown or ambiguous property name) or whether matches can return multiple properties.

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 usage trigger is correctly front-loaded and tightly worded. However, the second half is one very long run-on sentence enumerating return contents clause by clause, much of which restates what the output schema already declares. It earns partial credit for informativeness but costs readability.

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 only two parameters and an output schema present, the definition is nearly complete: trigger, inputs, and result scope are all covered. The main gap is what happens when the property name is ambiguous or unmatched, since a single-name lookup is prone to miss. The verbose return list is redundant against the output schema but not harmful.

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 both parameters are documented in-schema, so the baseline is 3. The description contributes a little: it confirms 'property' is shorthand for the name and that 'company' is an optional disambiguator, and the example names hint at expected naming conventions — but it adds no format or matching rules beyond the schema.

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 retrieval action on a specific resource — one mining project/property by name — and enumerates the facets returned (ownership, location, resources/reserves, studies, drill results). This clearly separates it from sibling find_mineral_projects (a search) and get_drill_results (a narrower slice).

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 trigger condition is explicit and concrete: 'Use this when someone asks about one mining project or property by its name', with example property names illustrating the granularity. It also tells the agent to supply the company 'if you know it', clarifying the optional parameter's role. It stops short of naming an alternative (e.g., use find_mineral_projects to discover or compare_peer_ownership to contrast), so 4 rather than 5.

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