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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful payload context (files, dependencies, install command) since no output schema exists, but it omits any error behavior, size/limits, or what 'in full' entails.

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?

A single tight sentence with no filler, leading directly with the resource. Slightly awkward phrasing ('the command that adds it to a project') costs it the top score, but nothing is wasted.

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 one-parameter idempotent read with no output schema, the description covers the return payload adequately but not fully: it doesn't say what happens on an unknown name, whether files are paged or truncated, or how the install command should be used. The annotations carry the safety story, leaving the description minimally sufficient.

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% and there is a single parameter, so the schema fully documents 'name' including its pattern and the example 'sign-in'. The description adds nothing about the parameter, which is the expected baseline when the schema does the work.

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?

Names the specific resource (a block) and enumerates what is retrieved: its files, the packages they require, and the install command. An agent can tell it fetches one block's detail. It falls short of 5 because it is phrased as a noun fragment with no verb and never distinguishes itself from get_chart/get_page/get_rules or explains its relationship to list_blocks.

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?

There is no explicit when-to-use, when-not-to-use, or alternative tool named. The only usage signal is implied: the tool reads a single block by name. The schema hints 'name from list_blocks', but that routing guidance lives in the parameter, not the description.

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