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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower. The description adds genuinely useful behavioral context beyond the schema: a flat 5-point cost per successful run, and a full inventory of the return payloads an agent can expect.

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?

Front-loaded with the verb and resource, and the long content enumeration earns its place by telling the agent what data comes back in the absence of an output schema. Slightly dense, but no wasted sentences.

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 no output schema, the description compensates well by enumerating return contents, and the single 100%-documented parameter needs no further detail. Cost is disclosed; usage routing to sibling tools is the only meaningful gap.

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 coverage is 100% and the schema already documents the sole 'sector' parameter with an example URL. The description's 'by URL or id token' merely restates that, adding no new syntax, format, or validation meaning, so the baseline of 3 applies.

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?

States a specific verb ('Get') and resource ('one Tracxn sector overview'), then enumerates the exact payload (company/funding/unicorn/IPO/acquisition totals, top companies and investors, trends, rounds, news). The sector-level scope is clearly distinguishable from sibling tracxn tools like run_tracxn_companies or run_tracxn_investors.

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 implies the usage context ('one sector overview') but never states when to choose this over alternatives such as run_tracxn_companies_search or run_tracxn_unicorns_search. No prerequisites, exclusions, or explicit routing are provided, so usage is only inferable.

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