find_entity_by_name

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description does add the matching strategy ('exact first, then contains'), which is useful behavior beyond the annotations. However, it says nothing about result ordering, limits, or whether it can return multiple matches.

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, front-loaded sentence with zero waste; the matching order is stated immediately. It is appropriately short for what it conveys, though brevity comes at the cost of the missing guidance noted elsewhere.

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 2-parameter read tool with annotations and no output schema, this is borderline complete. It omits what a match looks like and how many results may come back, and it leaves the ambiguity against search_entities unresolved.

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 50%: entity_type is documented in the schema, but the required 'name' parameter has no schema description. The description does not compensate, failing to clarify whether 'name' is a display name fragment, exact value, or identifier, nor how entity_type narrows the search.

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 (Find) and resource (entities) plus the matching key (display name). It does not distinguish itself from the closely named sibling search_entities, so an agent cannot tell them apart from the description alone.

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 indication of when to use this versus search_entities or get_entity, all of which exist in the sibling list. Usage is only implied by the verb 'Find' and offers no exclusions or prerequisite context.

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