history_get_recent

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

No annotations are provided, so the description carries the full disclosure burden. It does add valuable behavioral context - IDs are profile-local and must never be reused across profiles - but says nothing about whether this is a pure read, how many results come back, or what the ordering is, despite an output schema existing.

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 purpose and followed by the one constraint that will cause failures if ignored. Nothing is padded.

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 two-parameter read tool with an output schema, the description covers the only real footgun (profile-scoped IDs) and the prerequisite. The remaining gap is disambiguation from history_query, which an agent must guess at.

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 only 50% (profile_id is undocumented in the schema), and the description compensates by explaining where to obtain it and warning that object IDs are scoped to that profile. The count parameter is left to its schema default of 10, which is acceptable.

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?

States a specific verb and resource ('Get recent browser history') that an agent can act on immediately. It does not, however, distinguish itself from the sibling history_query, so the 'recent' qualifier is the only differentiator.

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?

Gives a concrete prerequisite (profile_id must come from profiles_list), which is real usage guidance. It never says when to prefer this over history_query or what 'recent' means in terms of a time window, so the when-to-use decision is only implied.

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