users_subscription_request_history

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds a concrete behavioral constraint: it returns only the 'recent 24 records', which prevents an agent from assuming full history. It lacks details on sorting or pagination, but the record cap is a valuable disclosure beyond annotations.

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 a single compact phrase with zero waste, and it front-loads the core action and the record limit. No extraneous details are present.

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 simple read with one parameter and no output schema, the description is minimally adequate. However, it does not explain what a 'request' record contains or how the 24-record limit is applied, leaving an agent with unanswered questions about the return shape.

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 description coverage is 0% and the description does not mention the required 'userId' parameter or its constraints (e.g., positive number). The word 'user' hints at the parameter, but no meaningful semantics are added beyond the schema's field name, leaving a significant gap for a required argument.

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 states a specific verb ('Get') and resource ('user subscription request history'), making the core action clear. It does not, however, differentiate from the similar sibling 'subscription_request_history_list' or 'subscription_request_history_stats', so an agent can't tell them apart without opening schemas.

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 phrase 'recent 24 records' gives implied scope for when this tool is useful (fetching a small recent history), but there is no explicit guidance on when to choose this over alternatives like 'subscription_request_history_list'. No prerequisites or exclusions are mentioned.

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