show_profile

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

Describes read-only behavior and null return when no profile is set. No annotations are provided, but the description discloses the key behavioral trait: it returns stored data without side effects.

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 sentences, zero wasted words. Purpose and usage guidance are front-loaded. Every sentence earns its place.

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?

No output schema, but the description fully explains what is returned (fields and null case). Given the tool's simplicity and zero parameters, the description 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?

Input schema has zero parameters, so the description carries full burden. It adds meaning by listing the specific fields returned (birth year, retirement target, etc.) and explaining the null case. Schema description coverage is 100%.

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?

Clearly states it reads the user's stored profile with specific fields (birth year, retirement target, etc.) and returns null if unset. Verb 'Read' and resource 'profile' are explicit. Distinct from siblings like show_portfolio or show_flow by focusing on personal goals.

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?

Explicitly says 'Use this to anchor analysis to the user's actual goals rather than generic advice.' Provides clear context for when to use, though no alternatives or exclusions are mentioned.

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