get_profile

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

No annotations are provided, so the description carries the full burden; it does convey that this is an aggregate read that surfaces curated facts rather than a mutation. However, it says nothing about whether the briefing is cached, how stale the facts may be, or what happens when no memories exist yet.

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?

A single front-loaded sentence with zero filler, and the session-start framing arrives first. It is efficient, though the brevity edges toward under-specification for a param-bearing tool.

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?

An output schema exists, so return contents need not be spelled out, and the tool is a simple one-parameter read. The unresolved gap is the undocumented `project` parameter and the lack of any handling note when the profile is empty.

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 single optional parameter `project` has 0% schema description coverage and is never mentioned in the description, so an agent cannot tell whether it scopes the briefing to one project or is merely a filter hint. With low coverage the description was expected to compensate and does not.

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 a specific resource and its contents: pinned memories, preferences and most-used facts, framed as a session-start briefing. That distinct aggregate framing tells an agent it is not the same as a single-item lookup like get_memory or recall, though no sibling is named explicitly.

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?

"Session-start" implies a narrow usage window, giving implicit guidance on when to call it. There is no explicit when-not statement, no mention of how it relates to siblings such as get_memory or recall, and no note on whether repeated calls within a session are wasteful.

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