feegow_list_patients

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

No annotations provided, so description carries full burden. Discloses HTTP GET method and pagination behavior. However, does not mention authentication, rate limits, or how full vs non-full differ in terms of response size or performance. Adequate but minimal.

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?

Extremely concise: one sentence covering purpose, pagination, and a key parameter option. No unnecessary words. Front-loaded with the tool's purpose.

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 list tool with 4 parameters and no output schema, the description explains pagination and view_mode but lacks details on query filtering, response format, default behavior, and error handling. Adequate but incomplete.

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?

Description adds meaning for limit, offset, and view_mode beyond the schema (e.g., 'Use limit/offset para paginar' and 'view_mode=full traz o cadastro completo'). However, the 'query' parameter is only described in the schema as additional key-value pairs, and the description does not clarify its usage or provided examples. Since schema coverage is 50%, description partially compensates.

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?

Clearly states it lists patients and mentions pagination and optional full mode. However, it does not differentiate from the sibling tool feegow_search_patient, which likely searches patients, but the distinction is not explicit.

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?

Provides guidance on using limit/offset and view_mode, but does not specify when to use this tool versus feegow_search_patient or other patient-related tools. No exclusions or alternatives mentioned.

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