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

Annotations already flag read-only, non-destructive, idempotent behavior. The description adds the valuable clarification that this is product information rather than account data, and describes the two-part return shape: canonical text plus a structured summary.

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?

Three sentences with no filler. The trigger condition is front-loaded, followed by the return contents and a clarifying scope note. 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?

For a zero-parameter, read-only informational tool with an output schema and full annotations, the description gives everything an agent needs: when to use it, what it returns, and how it differs from account-data tools.

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 zero parameters and the schema is fully covered, so parameter-level description is unnecessary. The baseline for no-parameter tools is 4; the description adds no irrelevant or missing parameter detail.

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 states a clear purpose: answer questions about what Dynamoi is, who it is for, and what it offers. It distinguishes itself from account-data tools by explicitly saying it returns product information, not account data.

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 gives explicit trigger conditions ('when the user asks what Dynamoi is, who it is for, or what it offers') and includes useful timing context ('including before sign-in or before choosing a tool'). It also provides an exclusion by clarifying it is not account data.

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