pm_export_users_csv

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

No annotations provided; description does not disclose side effects, authentication needs, rate limits, or that it's a read operation. The description only states the HTTP method and format, which is insufficient.

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 sentences covering method, format, and key parameter behavior. Could be improved by adding prerequisites or exclusions, but not overly verbose.

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 no annotations and low schema coverage, the description should provide more context about authentication, safe usage, and differentiation from similar export tool. Output schema exists but description does not leverage that to reduce burden.

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 7 parameters with 0% coverage. Description only explains 'fields' as comma-separated column names and vaguely references filters similar to pm_list_users. No detail on others like team_id, label_id, user_kind, etc.

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?

Clearly states it exports users as CSV and refers to pm_list_users filters. Distinguishes from pm_list_users (list vs. file) but not from pm_export_users_joined.

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?

Mentions same filters as pm_list_users, but no explicit guidance on when to use this tool vs alternatives like pm_list_users or pm_export_users_joined. No when-not-to-use guidance.

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