dooray_post_logs

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

With no annotations provided, the description carries the full burden. The verb 'find' implies a read-only operation, but the description does not explicitly state that it modifies nothing, nor does it mention pagination behavior or return format. It adds minimal context beyond the schema.

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, focused sentence with no redundant words. It is appropriately front-loaded and 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?

The description is too terse for a tool with six parameters and no output schema. It doesn't explain the 'operation' parameter, the meaning of 'comments and activity logs' in terms of return values, or how this relates to nearby log tools. The schema provides some structure, but the description should offer more context.

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 six parameters. The description adds no additional meaning about how parameters interact or what values are expected, so it stays at the baseline.

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 the specific verb 'find' and clearly identifies the resource as 'comments and activity logs of a Dooray post.' It distinguishes from sibling tools that create or update logs, but it doesn't explicitly differentiate from the singular dooray_post_log tool, leaving some ambiguity about whether this returns a list or a single item.

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. It simply states what it does, without mentioning when it should be preferred over dooray_post_log or how it relates to other log-related tools.

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