Get Activity

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

No annotations are provided, so the description carries the full burden: it doesn't state that this is a non-mutating read, whether the activity must exist, what happens on a missing ID, or how session scoping affects the lookup. Only the trivial 'read one entity' implication is conveyed.

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?

A single front-loaded sentence with no filler or repetition; nothing needs trimming. It is efficient, though the brevity reflects under-specification rather than discipline.

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?

An output schema exists so return values need not be described, but for a two-required-parameter lookup with zero schema descriptions and zero annotations, the description leaves too much unsaid about scoping and failure behavior to call it complete.

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% with three parameters (session_id, activity_id, _meta). The description mentions only 'ID' in the singular and never explains that a session_id is also required or how the two identifiers relate, adding essentially no meaning beyond bare property names.

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 (get) and resource (a single activity), and the singular 'single activity' implicitly contrasts with the list_activities and list_all_activities siblings. It loses a point because it says 'by ID' (singular) while the tool actually requires two identifiers, session_id and activity_id.

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?

No when-to-use guidance, no prerequisites, and no mention of the sibling list_activities / list_all_activities tools that would be the alternative for browsing activities. The agent must infer usage entirely from the name.

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