analyze_margin_trends

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

With no annotations, the description carries the full burden and discloses several behavioral traits: it reports margins as percentages, uses available annual history, orders oldest to newest, provides a delta, and deliberately refrains from labeling trends. This is strong behavioral context, though it could mention how missing years are handled.

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 compact and front-loaded, with no filler. Every sentence adds value, including the explicit note about not labeling trends, which prevents misinterpretation.

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?

Given the single required parameter and presence of an output schema, the description covers the essential semantics: scope, metric types, ordering, delta calculation, and the interpretation boundary. Nothing critical is missing for an agent to invoke it 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 schema provides zero description for the symbol parameter, but the description compensates with concrete examples ('RELIANCE', 'TCS.NS', 'TCS.BO') and the term 'ticker symbol,' which clarifies the expected format and exchange suffix conventions. This is sufficient for a single parameter.

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 clearly identifies the tool as tracking gross, operating, and net margins across an Indian equity's annual history, with a specific output of oldest-to-newest ordering and first-vs-latest delta. It is specific enough to distinguish itself from financial ratio and growth metric siblings.

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?

No explicit guidance is given for when to use this tool versus alternatives like calculate_financial_ratios or calculate_growth_metrics. The description explains what the tool does but not the conditions that should lead an agent to select it.

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