story

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only states the intended action but fails to mention any behavioral traits such as authentication needs, side effects, or return format. The mismatch between described parameters and schema further reduces transparency.

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 short sentence, which is concise but not effectively structured. It front-loads the action but omits critical details, and the brevity sacrifices clarity.

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 is incomplete given the lack of parameters, output schema, and annotations. It does not explain what data is returned, how to use it, or how it differs from similar tools like 'story' or 'get'. Essential context for agent invocation is missing.

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 description mentions 'username and ID' as parameters, but the input schema defines zero properties. This directly contradicts the schema and provides false information. Schema description coverage is 100% (trivially due to no params), but the description adds incorrect semantics, making it worse than useless.

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 'Getting story by username and ID' specifies a verb and resource, but the input schema has no parameters, making the stated purpose impossible to execute. It does not differentiate from sibling tools like 'stories' or 'get', and the lack of parameters undermines clarity.

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?

No guidance is provided on when to use this tool versus alternatives. Sibling tools like 'stories' (plural) and 'get' suggest overlap, but the description offers no context or exclusions.

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