danbooru_get_wiki_page

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

The description adds valuable behavioral details beyond annotations, such as conversion of Danbooru DText markup to plain text in markdown mode, truncation via body_limit, and error handling (404 for missing wiki page). Annotations already cover idempotency and read-only nature, so the description complements them well.

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 well-structured with clear sections (Args, Returns, Examples) and is front-loaded with the core purpose. Every sentence adds value, and there is no superfluous information. It is appropriately sized for the tool's complexity.

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?

The description covers the tool's purpose, usage, parameter details, return format (including a schema), error handling, and examples. With the output schema provided in the description and complete annotations, the description is fully adequate for an agent to invoke the tool 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?

The input schema already provides descriptions for all three parameters, so the baseline is 3. The description adds some contextual examples and explains the purpose of title (e.g., 'like a Danbooru tag'), but does not significantly enhance parameter understanding 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 it retrieves the wiki description for a tag and distinguishes itself from the sibling 'danbooru_get_character_profile' by noting that the sibling should be used for complete character info. It specifies the resource (wiki page) and the action (get), making the purpose very specific.

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 explicitly provides usage guidance by stating when to use an alternative ('For complete character info, use danbooru_get_character_profile instead'). It also includes examples that illustrate typical use cases, helping the agent understand appropriate contexts.

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