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

No annotations are provided, so the description must carry the full burden. It mentions billing cost ('1 Credits') but omits other behavioral details such as authorization needs, pagination behavior, or what happens with large result sets. This is a minimal disclosure.

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 two concise sentences with the purpose front-loaded. There is no redundant elaboration, and the billing note is a useful addition without adding clutter.

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 tool with no output schema and no annotations, the description is incomplete. It fails to explain the 'start' parameter, pagination, response format, or any usage limits beyond billing. The tool is simple, but the description leaves critical gaps.

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 explains that 'urn' is used to identify the profile, which adds meaning to that parameter. However, 'start' is not mentioned at all, and schema coverage is 0%, leaving the agent without any clue about pagination or offset semantics.

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 the action ('Get all'), the resource ('Articles'), and the scope ('for given profile by urn'). This distinguishes it from sibling tools like get_api_v1_articles_article_info and get_api_v1_articles_article_reactions, which target specific article details rather than all articles.

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 implies this tool is for retrieving all articles for a profile, which is clear context. However, it does not explicitly state when to use this over sibling tools like article_info or article_reactions, nor does it mention alternatives or exclusions.

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