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

readOnlyHint=true already establishes the safety profile, so the description's main added value is the id-vs-query mode distinction. It says nothing about pagination behavior, return shape (array vs single object), or whether filters are required, which matters for a query tool.

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?

One sentence, front-loaded action, zero filler. Both modes are conveyed without any repeated schema detail.

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 output schema, the description should ideally indicate the return form (single record vs list, and whether counts/pagination metadata are included). Instead it covers only input modes, leaving the agent to infer what comes back from a 500-record-capable query.

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?

At 83% schema coverage the schema already documents id, skip, sort, limit, and query well. The description only reinforces id and query semantics and adds nothing about sort/limit/fields beyond what the schema provides, so baseline 3 applies.

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 ('LimClassroomCourse records') plus the two retrieval modes, so an agent knows exactly what it returns. It doesn't explicitly differentiate from siblings like query_limclassroomstudent, but the resource name is inherently distinguishing.

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?

Explicitly maps the two calling modes: 'pass id for one record, or query for a filtered list,' giving a clear condition for each parameter path. It stops short of naming alternatives or exclusions, but the primary when-to-use guidance is present.

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