get_activity

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

The readOnlyHint=true annotation already establishes that this is a safe read, so the bar is lower. The description does add the one genuinely useful behavioral fact beyond the annotations: the payload is history-plus-comments, not the issue body itself. It says nothing about pagination, ordering, or truncation behavior implied by the limit parameter, which matters for a history feed.

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?

At seven words it is front-loaded with zero filler, which is good structure. But the brevity reads as under-specification rather than discipline — the single phrase carries no verb, no scope, and no qualifiers an agent can act on.

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 three parameters, a 33% coverage rate, and no output schema, the description should be carrying more weight than one line. It never explains pagination via limit, workspace scoping, or what the returned activity entries contain, so an agent can invoke it but not confidently predict the result.

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 coverage is only 33% — object is documented, but limit (default 50) and workspace are not. The description's "issue or object" merely echoes the existing object description and gives no meaning for limit (page size? cap? ordering?) or workspace scoping, so it fails to compensate for the coverage gap.

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 the resource ("change history and comments") and the target ("an issue or object"), so an agent knows roughly what comes back. However, it uses no verb ("get" only appears in the name) and draws no boundary against siblings like get_issue or changes_since, leaving overlap to inference.

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 guidance at all: nothing says whether this is for auditing field changes versus reading discussion threads, and no alternative is named. The agent must guess whether get_issue or changes_since is the better pick for a given question.

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