Get account

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is clear. The description adds useful scope by listing sensitive returned data such as email, buyer stats, unread messages, and favourites, but does not disclose additional behavioral traits like authentication requirements or rate limits.

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 front-loaded with a high-level summary followed by a detailed field enumeration. It is appropriately sized, though there is some duplication between the first sentence's mention of buyer stats/unread messages/favourite counts and the second sentence's elaboration of those fields.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does so thoroughly by enumerating member id, name, email, account type, location, currency, profile URL, unread messages, buyer stats, and favourite/watch counts. With zero parameters and full annotation coverage, the definition is complete enough for correct invocation.

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?

This tool takes zero parameters, so there are no parameter semantics to clarify. The baseline score of 4 applies because the schema has no parameters and the description does not need to compensate for missing parameter documentation.

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 uses a specific verb-resource pairing ('The signed-in PeoplePerHour account') and enumerates the returned fields, so the agent knows exactly what data this tool fetches. It also distinguishes itself from sibling tools like get_freelancer by emphasizing that it returns the account the tools act as, i.e., the current signed-in identity rather than another user.

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 clear context for when to use it: retrieving the signed-in account and the identity behind all tool actions. It does not explicitly name alternatives or when-not conditions, but for a zero-parameter self-account read, the practical ambiguity with siblings is low.

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