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

With no annotations, the description carries the full load and does real work: it discloses that NEAR articles, news and press releases come back in full while reprints and partner press come back as an excerpt with a source link, mirroring website behavior. It also explains the truncated-read/offset-continuation model, though it says nothing about error handling or any access constraints.

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?

Purpose and the field list are front-loaded in the first sentence, and each subsequent clause adds usable information about full-vs-excerpt content and pagination. A few phrases ('the same as the website') are chattier than needed, and the colon-heavy first sentence is slightly awkward.

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 three-parameter read tool with no annotations and no output schema, the description covers the essentials: what is returned, why some posts are truncated to excerpts, and how to page through long text. The main omission is what happens for an invalid or unpublished id.

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 the baseline is 3, but the prose adds a reading model beyond the field docs: it frames offset as continuing a long post past the first part. That complements rather than repeats the schema's character-position wording, and the id's provenance is reinforced.

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?

States a specific verb and resource ('Get one blog post by the id') and immediately names the return fields (title, kind, author, date, text). It also distinguishes itself from siblings by tying the id to 'list_blog_posts or search', so an agent can tell how this differs from the listing tool.

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 tells the agent where the required id comes from ('list_blog_posts or search gave') and when to use offset ('to keep reading a long post past the first part'). It does not state exclusions or failure conditions (e.g., unknown id), so it falls just short of a full when/when-not treatment.

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