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

Annotations already cover read-only, idempotent, closed-world safety, so the description adds the details annotations cannot: it requires a browser login, it mirrors the dapper://me resource, and the returned default country explains the fallback behavior of an omitted country_code elsewhere. No return shape discussion is needed because an output schema exists.

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?

Front-loaded with who/what, then usage, then auth. The opening sentence is dense with parenthetical lists, which is slightly heavy, but every clause carries information and nothing is padding.

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 tool with an output schema and full annotation coverage, the description supplies everything the remaining burden requires: auth requirement, content scope, resource equivalence, and how the returned ids are consumed downstream.

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?

Zero parameters, so the baseline is 4. The description still earns its place by explaining that the returned entity_id and commission_id values plug into list_regulations and list_bills, which is useful cross-tool semantics rather than parameter detail.

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 specific resource (the signed-in user's identity in Dapper) and enumerates its fields: email, default country, interest tags, watched entities and commissions. It also distinguishes itself from lookup siblings by explaining that it returns the ids those other tools accept.

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 two concrete situations: grounding a personal briefing, and explaining why a call was scoped a certain way. It doesn't explicitly name a sibling it should be preferred over (e.g. list_my_followed_bills or update_my_interests), so the routing guidance is clear but not exhaustive.

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