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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuine value by naming the returned fields (subject, due date, priority, assignee, patient) in the absence of an output schema, though it says nothing about pagination behavior or result ordering.

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 tight sentences: capability plus filters first, return shape second. No filler and nothing redundant.

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 seven optional params, an output schema absent, and annotations covering safety, the description covers the essentials by stating both filter scope and the fields returned. Pagination defaults are left entirely to the schema, which is acceptable but slightly thin for a list endpoint.

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 description coverage is 100% and all enum values are documented, so the schema carries parameter semantics. The description only restates the filter dimensions (patient, status, priority, type, assignee) without adding format or combination semantics, which is the expected baseline here.

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 resource (practice tasks) and the supported filter dimensions, so an agent knows this is a filtered read of the task collection. It does not explicitly distinguish itself from semble_create_task or semble_update_task, but the list/filter framing is unambiguous.

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?

Usage is implied by the filter enumeration — an agent infers it should be called to browse or search tasks. There is no explicit statement of when not to use it, nor routing to alternatives such as semble_update_task for mutations or semble_list_patients for patient lookups.

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