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

The description states the tool 'Starts monitoring the study if it was unknown,' which is a persistent server-side state change, while the annotations declare readOnlyHint=true and destructiveHint=false. The disclosure is genuinely useful, but it directly conflicts with the read-only claim, so per the contradiction rule this scores 1.

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?

Two tight sentences, front-loaded with what is returned before the side-effect note. No filler, no restatement of the title or name.

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?

With no output schema, the description does good work describing the returned fields, and it flags the monitoring side effect. However, for a five-parameter tool with zero schema documentation it omits all filter/pagination guidance (since, limit, event_types, include_baseline), leaving an agent guessing how to scope the query.

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% across five parameters (limit, since, nct_id, event_types, include_baseline), so the description carries the full burden and does not meet it: it never mentions nct_id, the date filter, the limit, or the event-type filter. 'Event type' appears only as a returned field, which could even mislead an agent into not using the event_types filter.

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 names a specific verb+resource: the recorded change history for a study, with the return contents spelled out (previous/new values, event type, dates, provenance). It is clearly distinguishable from get_clinical_trial and search_clinical_trials, though it never names a sibling to route against.

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?

Usage is only implied: an agent can infer this is the tool for inspecting what changed on a trial, but there is no explicit 'use this when...' versus the other five trial/search siblings, and no stated prerequisites. The note that monitoring starts when the study is unknown is useful context but is not framed as a guidance rule.

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