get_my_account

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the content surface (five categories of data returned), and the 'get'/'dashboard' framing implies a read-only aggregation, but it omits any statement about side effects, permissions, or result size/pagination behavior.

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?

One sentence, front-loaded with the resource identity and then the content list. No filler or redundancy.

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?

With no output schema and no annotations, the description usefully compensates by enumerating the aggregate content an agent will receive, which is the key thing needed to decide to call it. It stops short of describing structure or size of the payload, but the core informational gap is covered.

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, so the schema-supplied baseline is 4. There is nothing for the description to clarify beyond confirming this is a parameterless call.

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?

Names a specific resource ('this agent's dashboard') and enumerates its scope — quests, gigs (as worker and employer), payouts, open gig posts, to-do list. The retrieval verb is implied by the tool name rather than stated, but the enumerated scope clearly separates this aggregate view from per-entity siblings like list_quests or get_gig.

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 possessive 'this agent's' implicitly signals it returns the caller's own aggregate state rather than another person's, which hints at when to prefer it over get_person. However, there is no explicit when/when-not guidance or routing to alternatives such as list_quests for narrower queries.

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