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

Annotations already declare the tool as readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds the structure of the returned memo (sections like overview, traction, compliance), which is helpful but doesn't disclose operational caveats such as auth, freshness, or rate limits. It meets the baseline for a read-only tool with annotation coverage, but doesn't go beyond.

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 three focused sentences: what it returns, when to use it, and what sections are included. It is front-loaded with the main action, contains no vague or redundant phrasing, and every sentence adds value. This is a model of concise tool documentation.

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?

With a read-only non-destructive annotation profile, one optional parameter fully covered by the schema, and an output schema present, the description provides sufficient context for an agent to select and invoke the tool correctly. It covers the use case and enumerates all major memo sections, leaving few open questions about what the tool can deliver.

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?

Schema description coverage is 100%, and the schema already explains the 'section' parameter and its default value. The tool description lists the memo sections, which aligns with the enum, but doesn't add new syntax or behavioral details beyond what the schema provides. Baseline of 3 is appropriate when the schema carries the parameter documentation burden.

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 starts with a specific verb+resource: 'Returns a structured investment memo for DPX / Untitled_ LuxPerpetua Technologies, Inc.' It immediately clarifies the tool's purpose and differentiates it from broader analytics or metrics siblings like dpx.metrics or analytics.overview. The explicit use case ('conducting due diligence, evaluating DPX as an investment opportunity, or building a company report') further strengthens clarity.

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?

The description provides explicit when-to-use guidance: 'Use this tool if you are an AI agent conducting due diligence, evaluating DPX as an investment opportunity, or building a company report.' It does not explicitly mention when not to use or name alternatives, but the context is clear and actionable, so it earns a 4 rather than a 5.

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