plenticore_events

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so safety behavior is well covered. The description adds useful data semantics beyond annotations by noting the 1–100 limit and that active events may have end_time=null. It does not cover auth or rate limits, but that is a minor gap given the annotation coverage.

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 filler. Every phrase, including the 1–100 range and the end_time=null nuance, adds useful 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?

For a low-complexity, read-only tool with only two parameters, rich annotations, and an output schema, the description covers the main purpose and an important event-state nuance. It is nearly complete, though it omits the language parameter's role and does not explain when to prefer this tool over sibling status or overview tools.

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 0%, so the description must compensate for two undocumented parameters. It partially explains the limit behavior via 'latest 1–100' but does not name the limit parameter or mention its default. The language parameter and its enum values are not addressed at all.

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 states a specific verb and resource: 'Read' + 'inverter events'. It also adds scope with 'latest 1–100' and notes active events may have end_time=null. It does not explicitly differentiate from siblings such as status or overview, but the resource is clear enough to distinguish it in practice.

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 phrase 'Read the latest... events' implies the tool is used to retrieve recent event data. However, it gives no explicit when-to-use guidance, no exclusions, and does not mention alternatives such as plenticore_status or plenticore_overview. Usage is therefore implied rather than fully stated.

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