list_my_chats

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

No annotations are provided, so the description carries the full burden. It states the tool lists chats assumed by the authenticated user and supports pagination, but it does not disclose whether the operation is read-only, any ordering, or the state of chats returned (e.g., in attendance or archived). More behavioral detail would be beneficial.

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 sentence that is front-loaded with the core purpose. It is concise and to the point, with no extraneous information.

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?

The tool has no output schema, but as a list operation, the return format is important. The description does not specify what fields are returned or pagination metadata. Given the complexity (8 parameters) and sibling tools, the description is adequate but could be more complete by mentioning the output structure.

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%, so the schema already documents all 8 parameters. The description mentions 'optional filters and pagination' but does not add meaningful detail beyond what the schema provides. A baseline 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 clearly states the verb 'Listar' (list), resource 'chats', and scope 'assumidos pelo usuário autenticado' (assumed by the authenticated user). It also mentions filters and pagination, distinguishing it from siblings like 'list_in_attendance_chats' or 'list_inbox_chats' which likely have different scopes.

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 implies the tool is for listing chats taken by the authenticated user but does not provide explicit guidance on when to use it versus alternatives such as 'list_in_attendance_chats' or 'list_inbox_chats'. There is no mention of when not to use it or comparative context.

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