read_profile

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered without the description. The description adds useful scope detail ('today included', 'missed-day note', conditional rotation output) but says nothing about permissions, cost, or whether the payload is cached/stale.

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?

It is front-loaded with the resource being read, which is correct. However the rest is a single sprawling comma-spliced sentence listing every field, which forces the reader to parse a run-on enumeration rather than scan short clauses; a 5 would break this into grouped sentences.

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 parameters, the description carries the burden of describing returns, and it does so field-by-field including conditional branches (planned-today vs rotation progress). It is only incomplete in that it does not position this tool against the other zero-argument read tools in the same server.

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 there is no parameter semantics for the description to explain; the baseline of 4 applies. The description instead spends its budget on output content, which is the only remaining surface.

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-ish framing and resource ('Overview of the signed-in profile') and enumerates exactly what the payload contains, including the 7/30-day windows and rotation progress. It never differentiates itself from closely overlapping siblings such as read_me, read_account, or read_training_summary, so it falls short of a 5.

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?

'Start here.' is genuine implied guidance about call ordering, which is more than nothing. But no alternative is named and no when-not-to-use condition is given, so an agent cannot tell whether read_me or read_account should come first instead.

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