pyp6xer_list_activities

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the safety profile is clear. The description adds minimal behavioral context beyond 'filtering and pagination', but does not contradict annotations. It does not elaborate on rate limits, data scope, or what 'activities' mean in context.

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 short and front-loaded: 'List activities' immediately conveys purpose. Every word is essential. However, it could include more useful context (e.g., dependency on loaded file) without being verbose, so not a 5.

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?

The tool has an output schema, so return values need not be described. However, the description omits that activities come from a previously loaded XER file (cache_key parameter). This prerequisite is important for context. While siblings are listed, no comparison is drawn. Overall adequate but with notable gap.

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 all 7 parameters with detailed descriptions (100% coverage). The description's phrase 'optional filtering and pagination' is generic and does not add meaning beyond what the schema already provides. Baseline score of 3 is appropriate.

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 clearly states 'List activities' as the verb+resource. It adds 'with optional filtering and pagination' which provides specificity. However, it does not distinguish from sibling tools like pyp6xer_search_activities, which also lists activities but with full-text search.

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?

The description implies usage when a filtered, paginated list is needed, but it does not explicitly state when to use this tool versus alternatives (e.g., pyp6xer_search_activities, pyp6xer_get_activity). No when-not-to-use or exclusions are provided.

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