pyp6xer_list_activities

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

Annotations already provide readOnlyHint=true, so the description's minimal behavioral info is acceptable. However, it does not add context about default pagination behavior, rate limits, or the dependency on a loaded XER file, which would be useful.

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?

Extremely concise at 7 words, capturing the core function. No wasted text. However, it could benefit from a slightly more informative sentence without adding fluff.

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 description lacks critical context: it does not mention that a cache_key from a prior 'pyp6xer_load_file' call is required. With 7 parameters and an output schema, this omission limits completeness. It also does not describe pagination behavior beyond what the parameters imply.

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 100%, so parameters are well-documented. The description adds a high-level summary ('optional filtering and pagination') but no new meaning beyond what the schema provides. Baseline score of 3.

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 with optional filtering and pagination,' specifying the verb (list) and resource (activities). It distinguishes from sibling 'search_activities' by implying it returns all activities with filters, though not explicit.

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 guidance on when to use this tool vs alternatives like 'pyp6xer_search_activities' or other list tools. The description does not mention prerequisites (e.g., loading a file) or when filtering is appropriate.

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