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

With no annotations, the description carries the burden. It says 'Returns' implying a read-only operation and 'Takes no arguments' clarifying no side effects from parameters. However, it does not explicitly state that it has no side effects or that it is safe to call repeatedly. Minor gap but largely transparent.

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, front-loaded with the tool's purpose, and every sentence earns its place: the first lists content, the second gives usage guidance and alternative. No fluff.

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 simple informational tool with an output schema and no params, the description covers what the tool returns, when to use it, and the alternative. It is complete for the agent to select and invoke 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 input schema is empty and the description explicitly states 'Takes no arguments,' confirming the absence of parameters. With 0 params, baseline is 4; this description adds clarity by stating it explicitly.

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 ('Returns') and clearly specifies the resource ('company's identity and tagline, engagement types, contact addresses, key pages, track record'). It distinguishes itself from sibling tools by focusing on company info versus positions, work, or applications.

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?

Explicitly states 'Read this first if you are deciding whether this company fits a need' and directs to an alternative: 'use dynomatix_submit_enquiry to start a conversation.' This provides clear when-to-use and a sibling comparison.

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