dooray_account_members

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

With no annotations, the description must alone disclose behavioral traits. It only states the action without explaining return format, pagination, exact/partial matching behavior, or error handling. This is a minimal disclosure for a search operation.

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, front-loaded sentence with no unnecessary words. Every part adds value, and it is appropriately concise.

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's simplicity, the description is adequate but incomplete. It does not describe the return value, which is important since there is no output schema. The lack of annotations and output schema means the description should provide more context about call 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 100%, so the baseline is 3. The description adds slight context by linking 'member_name' and 'user_code' to 'by name or userCode', but it does not clarify that 'operation' must be 'find_member_id' or how optional parameters interact. The schema's own descriptions are largely tautological.

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 uses a specific verb 'find' and clearly identifies the resource as 'dooray account members', with search criteria 'by name or userCode'. It is clear what the tool does, but it doesn't explicitly differentiate itself from the sibling tool 'dooray_account_member' (singular), which might have a related purpose.

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 usage for finding members by name or user code, but does not provide explicit guidance on when to use this tool versus alternatives like 'dooray_account_member'. No exclusions or alternative references are given.

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