get_profile

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

With no annotations, the description must carry the behavioral burden. It does disclose one valuable edge case ("empty if never saved"), which tells the agent how to interpret a missing profile, but it says nothing about permissions, side effects, or whether the profile is cached/computed.

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 short sentence with the resource and the failure-mode caveat front-loaded; every word earns its place and there is no filler.

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?

Zero parameters, an output schema covering the return value, and the empty-profile case disclosed — nearly everything an agent needs to call it correctly. The remaining gap is the missing contrast with analyze_music_profile, which matters given both operate on the profile concept.

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 nothing for the description to disambiguate beyond what the empty schema already shows. Baseline 4 applies.

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 and resource ("Return the stored taste profile JSON"), so an agent knows exactly what it fetches. It does not explicitly distinguish itself from the sibling analyze_music_profile, leaving the read-vs-analyze distinction implicit.

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?

Usage is only implied: read this when you need the persisted profile. There is no explicit when-to-use or when-not-to-use statement, and no guidance on choosing this over analyze_music_profile or save_profile.

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