SearchEntity

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

No annotations are provided, so the description carries the full burden of explaining behavior. It discloses nothing beyond the word 'Search' — no read-only indication, no return behavior, no side effects, no context about entities or result semantics.

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 phrase is short, but this is under-specification rather than genuine conciseness. It has no structured information, no context, and no guidance, so compactness provides no real value.

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 no annotations, no output schema, and no parameter details, the description is the only information source and it covers almost nothing. An agent cannot determine what an entity is, what a search returns, or how to interpret the result. The definition is far too sparse to be 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?

The tool accepts zero parameters, so the schema and description need no param disambiguation. Baseline 4 is appropriate because there are no parameter semantics to explain.

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?

Description simply restates the tool name ('Search for Entity' = SearchEntity) without any detail on what an entity is, what kind of search is performed, or what criteria are used. It does not help distinguish SearchEntity from similar siblings like QueryEntity or SearchDocument.

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 guidance is given about when to use this tool instead of QueryEntity, QueryEntityFull, InternationalBusinessSearch, or other search-like siblings. No preconditions, filters, or alternative routing are mentioned.

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