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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavior: the exact scoring dimensions (quality, value, growth, safety, spread), the benchmark against the 500 largest US companies, and the one-strength/one-watch output shape. It also proactively states no login or personal data is required, which removes an adoption concern.

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 trigger condition before the input and output details, so an agent can decide quickly. The return enumeration is long but each item is informative; only mild trimming (e.g., the parenthetical dimension list) would tighten it.

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 carries the full burden of describing returns and does so concretely: score band, component subscores, weights, benchmark comparison, qualitative takeaways. Input shape, limits, and prerequisites (no login) are all covered, leaving nothing an agent needs unanswered before calling.

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 67%, with halal and currency already well documented in the schema, so the schema does most of the work. The description adds only the 60-item cap and confirms that shares and amount are optional per holding, but says nothing about default behavior when neither shares nor amount is given, or how currency interacts with amount. Adequate but not compensating for the coverage gap.

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?

Names the specific action (scoring a portfolio from 0 to 100) and the exact resource (user's holdings, stocks or funds), with concrete user phrasings like 'my stocks' or a broker list. The return summary (score, weights, benchmark comparison) makes the output unmistakable and separates it from siblings like check_halal or compare_stocks.

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 trigger condition is explicit and well-scoped: the user shares holdings and wants a score, an assessment, or what to watch. It also bounds input ('up to 60 holdings') and notes ETFs such as VOO/VWCE are supported. It does not name when to prefer a sibling tool (e.g., check_halal for a single holding, compare_stocks for side-by-side), so it falls short of a 5.

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