skills_listar

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

With no annotations, the description carries the full burden. It discloses that the tool lists real skills and agents along with their titles, which implies a read-only, non-destructive operation. However, it does not mention output format, whether pagination applies, or any authentication requirements, leaving meaningful behavioral gaps for a tool with zero annotation coverage.

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 a single, front-loaded sentence that efficiently conveys the core action and scope. The adjective 'reales' is slightly redundant but does not detract significantly from the concise structure.

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 annotations, the description should ideally explain return format or structure. It states that results include titles but does not clarify whether IDs, descriptions, or other fields are returned. It also fails to resolve the overlap with the sibling 'agent_list', leaving the agent with incomplete context for correct tool selection.

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 no parameters, so the baseline of 4 applies. The description adds no parameter information because none exists, but it correctly implies a no-argument listing operation.

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 states a clear verb 'Lista' and specific resources: '18 skills jurídicas y los 19 agentes autónomos reales del producto, con su título.' However, it does not differentiate this tool from the sibling 'agent_list', which likely serves a similar listing purpose for agents. The tool name 'skills_listar' conflicts slightly with the description's inclusion of agents, creating minor ambiguity.

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 explicit guidance on when to use this tool versus alternatives such as 'agent_list' or 'skill_ver'. The description merely states what it lists, leaving the agent to infer that it is for discovery purposes. No conditions, prerequisites, or exclusions are provided.

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