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

The description goes beyond the readOnlyHint annotation by detailing concrete limitations: cannot create/rename/delete profiles, change privacy, manage billing, set up teams, invite teammates, or connect third-party services. It also discloses that it returns static public information only and no user data, and reassures that nothing is written. This gives the agent a complete safety and behavior profile.

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?

The description is well-structured with a clear opening purpose, explicit trigger conditions, an IMPORTANT limitations section, and a return-safety note. It is slightly redundant at the end ('Read-only; nothing is written' repeats earlier statements), but the information is front-loaded and each section 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?

For a zero-parameter, read-only informational tool with an output schema and readOnlyHint annotation, the description is complete: it states the purpose, when to use it, what not to attempt, where to redirect users, and what kind of data it returns. Nothing essential is missing for an agent to select and invoke it correctly.

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 has no parameters, so the baseline of 4 applies. The description does not need to explain parameter semantics because there are none; it instead clarifies what information the tool returns, which is the relevant semantic content for this no-input tool.

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 uses a specific verb ('Explain') and names the exact resources covered: what UseMyContext is, what the connection can and cannot do, and where to manage the account. This clearly differentiates it from siblings like account, profile, or suggest_update by emphasizing it is informational and read-only.

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?

It explicitly states when to call: 'Call this when the user asks what UseMyContext is, what you (the AI) can do with this connection, or where to find pricing, plans, billing, teams, or settings.' It also gives clear negative guidance: the AI cannot perform account/admin actions and should instead point the user to returned links. This provides both inclusion and exclusion criteria.

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