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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower, and the description adds a real behavioral caveat: metadataFilters on scopes are silently ignored. It does not, however, describe the shape of the returned transition stats.

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: purpose first, then required/optional fields, then the caveat. Dense with implementation jargon (request type name, field-name note) but no wasted sentences.

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 6-parameter tool with deep nested objects and no output schema, the description covers invocation essentials but omits what the transition stats contain and any auth/prerequisite context beyond the schema's own notes. Adequate but with clear gaps.

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?

With only 33% schema description coverage, the description must compensate, and it does partially: it names the baseScope/coverageScope vocabulary, flags required vs optional, and warns that scope metadataFilters are ignored. It still leaves botId, projectApiKey, and the scope fields' semantics largely to the schema.

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'. It is distinguishable from siblings like get-truecoverage-event-details and get-truecoverage-child-event-tree by naming the transition/between-events scope, though it doesn't explicitly contrast with them.

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 tells the agent which fields are required (eventTitle, nextEventTitle, baseScope) and which is optional (coverageScope), plus a 'metadataFilters ignored' caveat, but gives no when-to-use guidance relative to the other truecoverage retrieval tools. Usage is implied rather than routed.

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