get_profile_context

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 usefully discloses the dual return payload (structured StoneWay.json and raw StoneWay.md) and flags reconciliation guidance, but says nothing about read-only status, auth requirements, staleness/caching, or error 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 sentences with zero filler, front-loading the usage trigger before the return description. Every clause 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?

An output schema exists, so the description is not obligated to explain return structure, and it still adds the reconciliation nuance. For a zero-parameter read tool the essentials are covered; the only real omission is differentiation from the sibling get_bio.

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 to document; the baseline for a no-arg tool applies. The description makes no misleading claims about inputs.

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 retrieval action and enumerates the exact content it covers (facts, tech stacks, bio info, links, active projects), so an agent knows what it returns. It does not, however, distinguish itself from the sibling get_bio, whose subject matter ('bio info') it explicitly overlaps.

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?

'Call this first whenever you need...' gives a clear priority/trigger signal for entry into the profile workflow. It stops short of stating when NOT to use it or naming an alternative for the overlapping bio case, so the get_bio ambiguity is left unresolved.

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