Teacher profile

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds real value by disclosing the return payload (profile fields plus priced courses), but says nothing about behavior for unknown slugs or about how the course list is bounded, so it stays at a baseline-plus level.

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 short fragments, with the resource and its contents front-loaded and the follow-up pointer kept to one line. The 'Next:' line reads a bit like an inline navigation hint rather than description prose, but nothing is wasted.

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 read-only, two-parameter tool with no output schema, the listed return fields provide most of what an agent needs to decide whether to call it. The only gap is edge-case behavior for an invalid or ambiguous slug.

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 100%, with the slug format and example already documented, so the schema already explains both parameters. The description only implicitly explains what 'limit' controls through 'their courses with prices' and adds no new parameter constraints, so it is a 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?

Names a specific resource (teacher profile) and enumerates the fields returned (bio, students, rating, teaching hours, links) plus the attached courses with prices, which clearly separates it from mkh_course, which handles a single course.

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 'Next: mkh_course for one of the courses' line gives a useful follow-up path, but there is no guidance on when to choose this over mkh_search, mkh_organization, or mkh_browse, and no stated precondition beyond the schema's note that the slug comes from a course.

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