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

With no annotations, the description carries the full burden and discloses no behavior: no side effects, no data source, no read-only guarantee, no return behavior. The only added claim is that the tool shares its name with an external catalog entry, which is not behavioral information.

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 text is short but the first sentence is a tautology and the second is an external pointer, so neither earns its place. This is under-specification rather than effective conciseness.

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?

Even though the tool is simple (no parameters, no output schema), the agent has no idea what metrics are fetched, for which portfolio, from what source, or what response to expect. The description is not complete enough to support correct invocation or result interpretation.

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 declares zero parameters, so there are no inputs the description needs to clarify; the empty schema is the complete contract. By the zero-parameter baseline, this dimension is not a weak point, though the description itself still adds no semantic detail.

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 only restates the tool name and references a live catalog URL; it names no verb, resource, or outcome. It does nothing to differentiate fetch_portfolio_metrics from the many other fetch_/get_ 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?

There is no statement of when to use this tool or when to prefer an alternative. The sibling list contains numerous analytics and metric tools, but the description offers no selection criteria.

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