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

Annotations already make clear this is a non-destructive, closed-world read, so the description is free to add substance: results are scoped to the signed-in user only, returned newest first, and include status plus the OmniSocials team's replies. Those are real behavioral details an agent needs to phrase an answer. Only return shape/pagination remains unstated, which is minor for a zero-parameter list.

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, front-loaded with the resource and scope, followed by the usage trigger. The parenthetical listing submission channels is the only candidate for trimming, but it clarifies that requests may originate from non-app surfaces, so it earns its place.

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 no-parameter, read-only list tool with full annotation coverage and no output schema, the description supplies scope, ordering, and returned content — enough for an agent to call it and describe results. It could be marginally stronger by noting whether the list can be empty or how to submit a new request via request_feature.

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?

The tool takes no parameters, so the baseline is 4. The description correctly implies the only implicit filter is the signed-in user, with no optional date or status filtering available, which is consistent with the empty input schema.

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 names the resource and its scope precisely: feature requests the signed-in user submitted, aggregated from the app, AI assistant, API, and CLI. It goes beyond the title 'List Feature Requests' by adding ownership scope and ordering, though it never names its natural counterpart request_feature, so the submit/list pair is left implicit.

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 gives an explicit trigger: 'Use it when the user asks what happened to a request.' That covers the main invocation case well. It stops short of naming alternatives or stating when not to use it, but the trigger is concrete enough for an agent to act on.

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