therapyportal_list_clients

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

The annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds useful disclosure about the response contents, saying it returns names and date of birth only and never contact details or identifiers.

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 description is compact and front-loaded, starting with the primary purpose before adding the parent/child clarification and the PatientId relevance. Every clause adds useful information without repetition.

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?

Given the low complexity, annotations, and complete schema coverage for the single parameter, the description provides enough context. It explains the returned fields and the key identifier an agent needs for sibling tools, with no output schema required.

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 only parameter is view, and the schema description coverage is 100% with a detailed enum explanation. The description does not mention view, but the schema fully documents it, so the baseline score of 3 is appropriate.

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 states a specific verb and resource: "List the clients (patients) linked to this TherapyPortal login." It clarifies the parent/child relationship and explains that the returned PatientId is used by the message and document tools, which distinguishes it from the sibling list/download/get tools.

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?

It gives clear context for using this tool: to retrieve clients and their PatientId for downstream message and document tools. It does not explicitly state when not to use it or name a direct alternative, but the usage context is clear.

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