feegow_list_diagnoses

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action and resource, without mentioning pagination, authentication requirements, rate limits, or any side effects. This is insufficient for safe invocation.

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 a single line containing a category tag and the HTTP endpoint. It is concise and front-loaded with the verb. However, it sacrifices useful information for brevity.

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 tool has no output schema, no annotations, and two parameters (including a loosely defined 'query' object), the description is incomplete. It fails to cover expected response format, filtering capabilities, or usage constraints, leaving the agent without enough context to interpret results.

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 50% (one param described, one not). The description adds no meaning beyond the schema—it does not explain the 'query' object's expected keys or the role of 'paciente_id'. The URL path hints at patient_id but not in the description.

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 clearly states the tool lists medical records/diagnoses of a patient, specifying the verb 'Lista' and resource 'prontuários/diagnósticos'. However, it does not differentiate from other list tools like feegow_list_procedures or feegow_list_prescriptions among the many siblings.

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 description provides no guidance on when to use this tool versus alternatives, no when-not-to-use instructions, and no mention of prerequisites or context. The agent is left to infer usage from the name and siblings.

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