Documentació d'un mètode o classe de mapicgc-gl-js

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool returns parameters, types, and descriptions, but it does not say what happens when the name is not found, whether matching is exact or fuzzy, or whether class docs include inherited methods.

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?

Two sentences, front-loaded with what is returned and followed by the usage condition. Every clause adds information without waste.

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-only documentation lookup with no output schema, the description is mostly complete: it explains what content is returned and when to use the tool. The main missing piece is not-found or fallback behavior.

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%, so the baseline is 3. The description nevertheless adds useful examples such as 'addGeocoderICGC' and 'Config.getConfigICGC', which illustrate class-qualified names beyond the schema's simpler 'addMarker' or 'Map.addMarker' example.

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 and resource: returns detailed documentation for a concrete mapicgc-gl-js method or class. The phrase 'quan ja saps (o intueixes) el nom exacte' implicitly distinguishes it from the sibling search_docs tool.

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?

Explicitly says to use this tool when you already know or can guess the exact function name. It does not explicitly name search_docs as the alternative for unknown names, but the condition makes the intended routing clear.

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