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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so "Read-only" merely restates structured data and earns no credit. The description adds no behavior beyond annotations: it does not say what fields come back, what happens if account_id is not the connected account, or anything about error/auth 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?

Two short sentences, front-loaded with the resource identity, with no filler or repetition. The brevity is appropriate in form even though the content itself is thin.

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, an undocumented required parameter, and a same-family sibling (get_profile) that this tool is easily confused with, the description should specify what is returned and how it differs. It leaves both gaps open, so an agent could pass the wrong account_id or pick the wrong sibling.

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?

There is one parameter (account_id, uuid) with 0% schema description coverage, so the description carries the full burden of explaining it. It says nothing about account_id, notably not that it should be the connected account's own ID, which is exactly the non-obvious constraint an agent could get wrong.

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 resource and scope ("the connected account's own profile"), which implies fetching the caller's own data rather than someone else's. But there is no explicit verb (retrieve/get) and no differentiation from the sibling get_profile, so the agent must guess which one targets the authenticated user versus an arbitrary 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?

"Read-only" is a safety property, not usage guidance. There is no statement of when to call this versus get_profile, and no indication of prerequisites such as needing an authenticated session or which account_id to pass.

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