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

With no annotations, the description carries the full burden of behavioral disclosure, yet it only states what the feed contains and does not indicate read-only status, auth needs, pagination, sorting, or behavior when positionId is omitted. It adds context about event types but not enough about how the tool behaves.

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 efficient sentence with the core purpose front-loaded and parameter notes appended. Every word earns its place.

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 tool is simple and the description covers purpose and parameters adequately. However, without an output schema or annotations, the absence of return-shape details and behavior for an omitted positionId leaves meaningful gaps for an agent.

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. It does name both parameters and adds the useful default of 30 for limit and the optionality of positionId, but it omits further semantics such as value bounds, formats, or what happens when positionId is not provided.

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?

Description names a specific resource ('engine event feed') and scopes it to a position, with a concrete list of event types (slices, funding collected, alerts, liquidation). This is specific enough to distinguish it from sibling agent tools such as agent_status or agent_decisions.

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 context of use is implied: retrieve the event feed for a position. However, there is no explicit when-to-use or when-not-to-use guidance, nor any mention of alternatives among the many sibling tools, so the agent must infer selection.

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