listar_glossario

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

No annotations exist, so the description must disclose behavioral traits. It only states 'list all available glossary terms', implying a read operation, but does not explicitly confirm non-destructiveness, pagination, authentication requirements, or rate limits. Important behavioral details are omitted.

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 description is extremely concise with only two sentences. The purpose is front-loaded, and every word adds value. There is no extraneous content, making it efficient for an AI agent to parse.

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?

Given the tool's simplicity (one optional parameter, list operation) and the presence of an output schema (not shown but noted), the description sufficiently covers the tool's functionality. It lacks mention of ordering or size limits, but for a straightforward glossary listing, it is nearly complete.

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 input schema has 0% coverage, so the description must add meaning. It lists the 'lang' parameter with possible values 'pt', 'en', 'es' and a default. This adds value beyond the bare schema, but it does not explain behavior for invalid codes or how the language selection affects results.

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 clearly states 'List all available glossary terms', specifying the verb 'list' and resource 'glossary terms'. This distinguishes it from siblings like 'get_glossario' (singular retrieval) and 'search_glossario' (search), which operate on the same resource but with different actions.

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 guidance is provided on when to use this tool versus alternatives. It does not mention that this returns the full list, while the sibling tools like 'get_glossario' retrieve a single term or 'search_glossario' performs filtered searches. The description lacks context for usage decisions.

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