my_steam_recent_activity

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

With no annotations provided, the description carries the full behavioral disclosure burden. The word 'Get' indicates a read-only operation and 'my' implies auth-scoped data, which is helpful but minimal. The description does not disclose how 'recent' is defined, whether Steam credentials must be configured, or what happens when there is no activity.

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?

A single, direct sentence that front-loads the action ('Get') and names the resource without filler. Every word contributes meaning and the description is neither padded nor clipped.

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 zero-parameter read tool with an output schema, the description is minimally sufficient. However, it does not clarify the relationship to the similarly named get_steam_recent_activity, which is a notable contextual gap in a large sibling list. The output schema likely covers return details, but usage context is thin.

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 zero parameters and the schema confirms this with an empty properties object, so there is little for the description to add. The 100% schema coverage plus no parameters means the baseline of 4 is appropriate.

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 the verb 'Get' and a specific resource: the user's recent Steam gaming activity. 'My' clearly indicates this is scoped to the authenticated user, which adds useful specificity. However, a near-identical sibling tool named get_steam_recent_activity exists, and the description does not explain how the two differ, preventing a 5.

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 description provides no guidance on when to use this tool instead of the sibling get_steam_recent_activity. It does not mention authentication prerequisites, alternative tools for detailed Steam statistics, or exclusions. An agent must infer the meaning of 'my' and the tool name rather than being told when to select it.

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