get_activity

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

Although no annotations, description clearly indicates read operation ('Read'). Specifies return value (JSON string with full metadata). No contradictions. Could mention auth requirements but acceptable for a simple getter.

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?

Four concise sentences, front-loaded with purpose. Every sentence adds value without 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?

For a simple resource retrieval tool, description covers purpose, prerequisite action (list_activities), and output nature. Output schema exists, so return format is fully specified.

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 0%, description adds basic meaning ('Activity ID') but no format or constraints beyond schema. Adequate but minimal compensation.

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?

Explicitly states 'Read a specific activity (full metadata)'. Differentiates from sibling 'list_activities' by advising to use it first to find IDs. Clear verb plus resource.

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?

Provides explicit guidance to use list_activities first to find IDs, indicating when to use this tool. However, lacks explicit when-not or alternative scenarios.

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