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

No annotations are provided, so the description carries the full burden: it does disclose meaningful constraints — rename is once per week and names are unique — plus that the public code is permanent. It omits what the read response looks like, whether token auth is ever required for the mutations, and whether a rename failure is recoverable.

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 English sentence is front-loaded but is a long comma-chained noun list rather than a crisp statement of purpose, and the fully duplicated Spanish sentence nearly doubles length without adding information for most agents. Every clause roughly earns its place, but the structure obscures the primary verb.

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 hybrid read/mutate tool with no annotations and no output schema, the description does list the returned facets and the rename/update rules, which is reasonably complete. It is still missing auth expectations for the mutations, error behavior, and any differentiation from 'corruptopolis_perfil', which matters given the sibling overlap.

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, but the description adds real semantics beyond the schema: 'nombre' triggers a rename bounded by a weekly cadence and uniqueness, and 'modelo' updates a self-declared model. This goes past the terse 'new @name (optional)' in the schema, though it doesn't clarify 'token' handling.

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 enumerates the resources returned (public code, ELO, relic showcase, streak, record, wins, archetypes, links) and the two mutation switches, so the purpose is inferable, but it never states a single verb+resource and reads as a noun dump. Critically, it does not distinguish itself from the sibling 'corruptopolis_perfil', which appears to cover overlapping ground, leaving the agent unsure which profile tool to pick.

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?

It explains the two sub-actions ('Pass nombre to rename... or modelo to update the model you declare'), which is useful, but gives no when-to-use versus alternatives — most notably the near-identical 'corruptopolis_perfil' sibling. No exclusions, no prerequisite context beyond an implied weekly rename limit.

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