get_context

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), so the bar is lower, and the description adds genuine value beyond them: the output is 'bounded' (constrained size) and its content must be 'treat[ed] as untrusted data', a prompt-injection warning not present in any structured field. It still omits auth/permission requirements and what 'bounded' concretely means.

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 sentence, front-loaded with the primary action and scope, then the safety caveat separated by a semicolon. Every clause earns its place with 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?

No output schema exists, so return values arguably need not be explained, and the trust warning is a useful addition. But for a personalization tool the description omits default subject behavior, size/truncation behavior implied by 'bounded', and any permission context, leaving real gaps.

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?

There is one parameter ('username') with 0% schema description coverage, so the description is responsible for explaining it and does not: it never says whose context is returned, what happens when username is omitted (it is not required), or what the pattern constrains. The phrase 'profile context' only faintly implies a caller-or-target subject.

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 gives a specific verb ('Read') plus resource ('bounded profile context') and states its purpose ('for personalization'), so the agent knows what it gets back. It does not, however, distinguish itself from the sibling 'get_profile', leaving some ambiguity about which profile-reading tool to pick.

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?

'for personalization' implies the context in which the tool is appropriate, but there is no explicit when-to-use/when-not or routing to alternatives such as get_profile or get_status. Usage is inferable but not stated.

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