find_entities_by_property

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose one useful trait — matching is exact, not fuzzy or substring — but says nothing about case sensitivity, scope (all entities vs. current document), pagination, or result shape for what is clearly a query operation.

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?

A single tight sentence with the mechanism front-loaded after the core action. No filler, no restatement of the tool name.

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 two-parameter lookup with no annotations, no output schema, and zero schema description coverage, the description leaves important gaps: which entity types are searched, the search scope, and what is returned. It is usable but under-specified for its complexity.

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 0%, so the description must compensate. It does add genuine meaning by clarifying that 'property' can be either a direct entity field or a property-bag key, and that 'value' is matched exactly. However, it never explains valid field names, the value's expected type (the schema leaves 'value' untyped), or key syntax.

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?

Clear verb+resource (find entities) with the distinguishing mechanism spelled out: 'direct field or property-bag value using exact matching.' An agent can tell it apart from find_entities_by_layer by the lookup key, though the description never explicitly names the sibling tools it competes with.

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 guidance, no prerequisites, and no mention of siblings like find_entities_by_layer, find_entities_in_region, or list_entities. Usage is only implied by the verb, leaving the agent to infer when this lookup is preferable.

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