events_get_all_by_org

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

No annotations provided, so description must fully disclose behavior. It states a read operation but omits details like pagination, rate limits, permissions, or whether all events are returned at once. The behavioral disclosure is 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?

The description is a single 6-word sentence, very concise and front-loaded. However, it may be too terse, omitting useful context like return type or pagination, so not perfect.

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?

No output schema exists, so the description should clarify what is returned (e.g., a list of event objects with fields). The tool has moderate complexity (2 params, one nested) but the description provides no information on return values, making it 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?

Schema coverage is 100% with both parameters described. The description adds no additional meaning beyond the schema; 'for a specific organization' matches the 'organizationId' parameter. Baseline 3 is appropriate as schema already documents the parameters.

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 'Get all events for a specific organization' clearly states the action and resource, distinguishing it from siblings like 'events_get' (single event) and 'events_get_all' (all events without org filter). However, it could be more precise about scope (e.g., 'all events in the organization' versus 'events for the organization').

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?

No explicit guidance on when to use this tool versus siblings. Sibling tools like 'events_get_all' (no org filter) and 'events_get_by_org' (similar name) are present, but the description does not contrast them or provide when-not-to-use advice.

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