Search Hocametre Instructors

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

No annotations are provided, so the description carries the burden. It explicitly discloses that the data source is public, that no login is required, and that duplicate profiles are possible, and the search/return behavior is clear. It omits rate limits or pagination details, but those are minor for a simple read-only search.

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 concise sentences with no filler. The primary action and output are front-loaded, followed by the no-login requirement and duplicate-profile caveat. Every sentence earns its place.

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 simple 2-parameter search tool with an output schema, the description covers purpose, auth requirement, duplicate caveat, and output shape. It could mention limit behavior or route to sibling tools, but the core information needed to invoke it correctly is present.

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 descriptions are absent at 0% coverage, and the description compensates for the 'query' parameter by specifying it is a partial instructor name. However, 'limit' is not explained beyond its name and default, so parameter semantics are only partially addressed.

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?

The description clearly states the operation: search public hocametre instructor ratings by partial instructor name and return matching profiles with slugs. It is specific and informative, though it does not explicitly differentiate it from similar siblings like hocametre_lookup_instructors.

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 description gives clear when-to-use context: search public ratings by partial name, no login required, and be aware of duplicate profiles. It does not name alternative tools or exclusion cases, so it stops short of a 5.

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