ncloud_get_activity_detail

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

Description discloses that it performs a query with a narrow time range, which is behavioral context beyond the readOnlyHint annotation. It aligns with the read-only nature and adds useful implementation detail.

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?

Two concise sentences that are front-loaded with purpose. No redundant words, and the description efficiently conveys the tool's function.

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 retrieval tool with two parameters and no output schema, the description provides adequate context about inputs and mechanism. It lacks details on return format, but that's acceptable given common patterns.

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?

Input schema covers both parameters with descriptions. The description adds context by mentioning 'narrow time range' for eventTime and 'filter by activityId' for activityId, enhancing understanding beyond schema alone.

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?

Description clearly states it gets detailed information about a specific cloud activity event by querying with a narrow time range and filtering by activityId. It is specific about the action and resource, but does not explicitly differentiate from similar siblings like ncloud_search_event_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 explicit guidance on when to use this tool vs alternatives. The description implies use when activityId and eventTime are known, but does not mention when not to use it or suggest other tools like search_events for broader searches.

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