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

readOnlyHint=true already tells the agent this is a safe read, so the description's remaining job is to add context. It does add the return-field inventory and the underlying endpoint (Neon: GET /activities/{id}), which is genuinely useful since there is no output schema. It says nothing about behavior for a missing/invalid id (e.g. 404) or rate limits, so it is solid but not rich.

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?

One front-loaded sentence that names the resource, defines it, and lists the payload, followed by the endpoint. No filler or redundancy.

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 field enumeration is the right compensation and covers what the caller receives. For a single-id read with annotations already declaring read-only behavior, little else is strictly needed, though error handling for an invalid id is unaddressed.

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 100% for the single activity_id parameter, so the schema already carries the burden and the baseline of 3 applies. The description only restates the id via the REST path template and adds no format or sourcing guidance beyond it.

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 ('Fetch one activity') and disambiguates the entity with a parenthetical definition ('a logged interaction or task'). It also enumerates the payload fields (subject, note, dates, linked accounts, assigned users, status, priority), so an agent knows exactly what it gets that the list/search siblings would not.

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?

There is no when-to-use or when-not guidance and no named alternative, even though siblings such as neon_search or a list-activity tool could also surface activities. The only implicit signal is the required activity_id, which implies 'use when you already have an id' but is never stated.

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