leer_ideaFetch a specific idea and its comments by 24-character hexadecimal ID to inspect or build on a creative concept in the collective idea bank.
Lee una idea concreta por su id, con sus comentarios.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Id de la idea (24 caracteres hexadecimales) |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds one useful behavioral fact — that the response includes the idea's comments ("con sus comentarios") — but omits error behavior for an invalid id and any return shape detail.
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 short sentence with zero filler, front-loading the action and the scoping key. Every clause earns its place.
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 one-parameter read tool with annotations and full schema coverage, the definition is nearly complete; it even notes that comments are included. Without an output schema it could say a bit more about failure modes (unknown id), but nothing essential 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?
Schema coverage is 100% and the single id parameter is fully documented in the schema (24 hex chars). The description only restates "por su id" without adding format or constraint information, so the baseline 3 applies.
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 ("Lee") and resource ("una idea concreta") scoped by id, which implicitly distinguishes it from the plural sibling leer_ideas. It does not explicitly name or contrast with that sibling, so it stops short of a 5.
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?
Usage is only implied: the singular "una idea concreta por su id" suggests retrieval of a single known item, contrasting with leer_ideas/buscar_ideas. There is no explicit when-to-use statement or named alternative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.