Read one native Community member report

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered. The description adds that native report permissions apply, which is useful auth context, but does not explain return behavior or the fixed route mapping beyond the enum.

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 short sentences, front-loaded with the key constraint, with no filler. However, the phrasing is somewhat cryptic ('retained legacy selector mapped to...') and could be clearer.

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 read-only selector with full annotation coverage and 100% schema coverage, the description is adequate but does not explain how this tool relates to the four sibling analytics tools it shadows, leaving an agent uncertain about which to call.

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% and the enum is documented in the schema, so the description has little to add. It mentions 'four fixed reviewed native Pro report routes' but does not clarify how the enum values map to those routes, adding marginal value.

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 says it maps a selector to 'four fixed reviewed native Pro report routes', which implies a read operation, but never names what is being read (community member reports). The title partly compensates ('Read one native Community member report'), yet the description itself doesn't clearly state the resource or action, and the sibling tools already include explicit per-report tools (fc_analytics_top_members, etc.), which this selector shadows without clear differentiation.

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?

It notes 'Not a whole-community analytics export' but gives no positive guidance on when to use this selector versus the sibling per-report tools or the dashboard stats. No conditions, prerequisites, or exclusions are stated.

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