list_event_metadata

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, covering the safety profile. The description adds context about the 'configured ThinkingData project' but does not disclose behavioral traits such as pagination, rate limits, or scope of returned metadata. With annotations present, the description adds some value but stays within expected limits.

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, clearly front-loaded sentence with no redundancy or filler. Every word earns its place, and it efficiently communicates the tool's purpose.

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 zero parameters and an output schema is present, the description is complete enough. It states the resource being listed and the project scope, while return-value details are handled by the output schema. No additional context is necessary for this low-complexity tool.

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?

The tool takes no parameters, and the input schema is an empty object. Per the rubric, 0 params yields a baseline of 4. The description correctly avoids inventing parameters and does not need to explain anything beyond the schema, which is fully covered.

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+resource ('List event metadata') and clearly distinguishes from the sibling tool 'list_property_metadata' by focusing on events rather than properties. The qualifier 'for the configured ThinkingData project' provides project scope, making the purpose unambiguous.

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 when event metadata is needed but offers no explicit guidance on when to choose this tool over alternatives like 'list_property_metadata' or the various analysis queries. There is no mention of exclusions or prerequisites, so guidance is minimal beyond the obvious function.

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