wattpad_get_story

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is well covered. The description adds that it returns a string containing the story card and chapter table, and advises using chapter IDs with another tool. This is useful but does not disclose details like pagination, authentication, or response differences.

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: a one-sentence purpose, a one-sentence sibling pointer, and a return type line. No filler or redundancy; the most important information is front-loaded.

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 read-only tool with a simple purpose, complete schema, and existing annotations, the description covers the essential workflow: it says what is returned and how to proceed to read individual chapters. Minor gaps like markdown/json differences are already handled by the schema's response_format parameter.

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 description coverage is 100%, so all parameters are documented in the schema. The description does not enrich parameter understanding; the only cross-reference ('Use el id de capitulo con wattpad_get_part_text') refers to the output, not input parameters. Baseline 3 is appropriate.

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 specific verb and resource: 'Obtiene la ficha de una historia con la lista de sus capitulos' (gets the story card with its chapter list). It differentiates from the sibling tool wattpad_get_part_text by advising to use that tool for reading chapter text, so an agent can tell them apart.

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 points to wattpad_get_part_text as the alternative for reading text, implying this tool is for metadata and chapter listing. It does not cover all sibling comparisons but gives clear situational guidance for the most relevant alternative.

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