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

With no annotations provided, the description carries the full behavioral burden. It does disclose return behavior ('bounded entity context with relationship IDs') and that ranking occurs, but says nothing about read-only/non-destructive nature, permission requirements, or performance. 'Find/rank' implies a safe read, but the safety profile is left to inference.

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, purpose front-loaded ahead of the sibling pointer, with zero filler. Every clause earns its place by either describing the operation or routing to the alternative.

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 is moderately complex (4 params, nested weights, output schema), and the description covers purpose, return shape, and the handoff to get_entity; the output schema removes any need to explain return values. It falls just short of complete by not clarifying the boundaries against the other finder siblings.

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 100%, including documentation of the nested weights object and enum-like entity type list, so the schema does the heavy lifting. The description adds no parameter-level detail (no mention of limit bounds, weights, or type filtering), which is acceptable at full coverage but yields the baseline 3.

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 ('Find and rank schema.org entities from natural language') and explicitly routes the agent to get_entity for full detail, which cleanly separates it from that sibling. However, it does not differentiate itself from find_by_type or search_content, which also retrieve entities, leaving some ambiguity about which finder to pick when the query is not clearly natural language.

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 phrase 'from natural language' implicitly defines the condition that selects this tool, and 'use get_entity for full detail' names the alternative and the reason to switch. It stops short of stating exclusions versus find_by_type or search_content, so no explicit when-not guidance.

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