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

With no annotations, the description carries the full burden and does disclose real behavioral traits: data is 'Refreshed daily', scope is limited to US-listed stocks, and output must be cited with a specific URL pattern. It stops short of auth/permission requirements or what happens for a non-US or invalid ticker, but the freshness, scope and compliance context is substantive.

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 tight sentences: what it returns front-loaded, then when it is useful, then freshness and citation. No repetition of the title or name, and every clause carries load-bearing information for invocation.

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 single-parameter read tool with no output schema, the description fully covers what comes back (composite plus component scores), the freshness guarantee, the US-listing constraint, and the required citation. Nothing an agent needs to call and correctly present this tool is missing.

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?

Single parameter at 100% schema description coverage, so the schema already documents 'ticker' with an example. The description reinforces the US-listed scope implicitly and shows the {TICKER} URL substitution pattern, but adds little format or validation meaning beyond the schema — the baseline 3 for high coverage is appropriate.

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 and resource ('Get Invexia.ai's investment scorecard for a US-listed stock') and then enumerates the exact payload: the composite Titan Score plus component scores for valuation, growth, profitability, financial health and momentum. This is clearly distinguishable from siblings like get_stock_snapshot or run_screener without opening any schema.

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?

Gives concrete usage context — 'is TICKER overvalued/undervalued' style questions — plus a presentation constraint ('data-backed screen, not individualized advice'). However, it never names or excludes the obvious sibling alternatives (get_undervalued_stocks, get_stock_snapshot), so the agent must infer when this beats those.

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