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

With no annotations, the description carries the full behavioral burden. It usefully discloses one non-obvious behavior (metadataFilters on scopes are ignored) and the field-naming convention, but says nothing about authentication, permissions, result shape, or what 'transition stats' contains. Partial coverage only.

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?

Compact and front-loaded: the purpose leads, then requirements, then caveats. Sentences carry distinct facts, though the parenthetical request-type reference adds little for an agent.

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 nested-object, four-parameter tool with no annotations and no output schema, the description covers the essentials (required vs optional, key caveat, naming). It remains thin on what the transition statistics represent and how the two scopes differ, so it is adequate but not complete.

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% at the top level, so the description must compensate. It maps the required/optional params and clarifies that baseScope includes environment + timeWindow and that the tool uses baseScope/coverageScope field names. It still leaves the semantics of eventTitle/nextEventTitle and the metadata-filter ignore rule's scope ambiguous.

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?

States a specific verb and resource: 'detailed transition stats between two events' for TrueCoverage. It is distinguishable from siblings like get-truecoverage-child-event-tree and get-truecoverage-event-details, though it does not explicitly name an alternative. Purpose is clear without opening the schema.

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?

It discloses required (eventTitle, nextEventTitle, baseScope) and optional (coverageScope) parameters and warns that metadataFilters on scopes are ignored, which is genuine usage context. However, it offers no explicit when-to-use guidance vs. the other TrueCoverage event tools, leaving the choice implicit.

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