read_portfolio

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description contributes the useful disclosure that output is a merge of a remote site and a local curated file, which explains non-obvious result composition, but it says nothing about caching, network failure behavior, or return shape.

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?

A single front-loaded sentence that carries the source information with no filler. It is appropriately sized for a no-argument read tool, though the parenthetical file reference is slightly dense.

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 and no parameters, the description is the only place an agent could learn what comes back. It identifies the data sources but not the returned structure (parsed site fields, the proyectos/software/eventos sections), leaving a moderate gap for a read tool that merges two sources.

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 tool takes zero parameters, so the baseline of 4 applies. The description correctly signals there is nothing to configure per call, other than implying PORTFOLIO_URL is environment-level configuration.

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 gives a specific verb+resource ('Read and parse the configured portfolio site') and even names the underlying data sources (PORTFOLIO_URL, data/portfolio-extra.json). That distinguishes it from read_cvlac and read_profile, though it does not explicitly contrast itself with those 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 when-to-use or when-not-to-use guidance is provided. An agent cannot tell from the text whether this should be preferred over read_profile or read_cvlac, or whether it must be preceded by login.

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