wikisync

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

With no annotations, the description carries full burden. It correctly identifies the tool as read-only ('Read') and discloses the critical dependency (WikiSync plugin) and data freshness condition (only updates when logged in). It does not mention rate limits or auth, but the provided information is sufficient and accurate.

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, extremely concise. The first sentence states the primary action, the second adds crucial context about scope and dependency. No unnecessary words.

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 that an output schema exists (so return format is documented) and the tool has only 3 simple parameters, the description adequately covers data source dependency and scope. It distinguishes from the sibling tool and explains the snapshot nature, making it complete for an agent to invoke correctly.

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 parameters are already documented. The description adds context about what WikiSync covers, which helps understand the 'section' parameter possibilities, but does not provide new parameter-specific information beyond the schema.

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 'Read public WikiSync character data for an OSRS account', specifying a concrete verb and resource. It lists the exact categories covered (quests, diaries, skills, etc.), making the tool's purpose distinct from the sibling 'player_skills' which likely focuses only on skills.

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?

The description explains that data is a snapshot dependent on the WikiSync RuneLite plugin, giving important usage context. However, it does not explicitly state when to use this tool versus the sibling 'player_skills' or other alternatives, nor does it provide exclusions.

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