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

The annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful context by saying it returns the original request parameters and paginated entity IDs, and that it does not spend credits, which is not covered by annotations.

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 appropriately short and front-loads the key retrieval behavior. The opening 'Get activity' is redundant with the tool name, but the remaining sentences earn their place by describing return contents and cost behavior.

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 rich annotations, one parameter, and no output schema, the description is largely complete: it says what record is retrieved and what the response includes. It could be stronger if it mentioned error behavior or pagination mechanics, but no major gap prevents correct invocation.

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?

There is only one required parameter, and the schema includes an example and short description for activity_id. However, the reported schema description coverage is 0%, and the tool description adds no extra guidance on how to obtain or format the activity ID.

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 states a specific verb and resource: retrieve the full details of a specific activity record. It implies retrieval by ID, distinguishing it from activity-search siblings, but does not explicitly name or contrast with those alternatives.

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 description implies that this tool is for fetching a known activity record when full details are needed, but it gives no explicit when-to-use guidance, prerequisites, or alternatives such as searching for an activity first.

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