get_activity

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

The description says 'Get,' implying a read-only operation, but with no annotations, it carries the full burden. It does not disclose side effects, authentication requirements, rate limits, or that it is safe. The behavioral context is minimal.

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 very concise (one sentence) but lacks the information to be useful. It is under-specified, which harms its value rather than being efficiently minimal.

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?

Given the tool has 3 parameters, no output schema, and no annotations, the description is extremely incomplete. It does not explain what a 'background activity' is, what the return value contains, or how to use the parameters. The tool is not adequately defined for reliable agent use.

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 has 3 parameters (activity_id, env_id, agent_token) with 0% description coverage. The description provides no information about these parameters beyond what the schema structure shows. The agent cannot infer their meaning or usage.

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 'Get a specific background activity' clearly indicates the verb (Get) and the resource (specific background activity). It suggests differentiating from list_activities which retrieves all activities. However, it does not explicitly state that it retrieves a single activity by 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 usage guidance is provided. The description does not mention when to use this tool versus siblings like list_activities, cancel_activity, or others. The agent is left to infer from the name alone.

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