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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without help from the text. The description adds only a content-domain caveat ("Education only, not financial advice"), which is useful framing but is not a behavioral trait of the tool itself; nothing is said about return shape or error behavior.

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?

Two short sentences, front-loaded with the operation and scope, with no filler or repetition. The second sentence is a liability disclaimer rather than tool guidance, which is borderline but short enough not to obstruct the core statement.

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 trivial single-parameter read tool with a full output schema and complete annotations, the definition supplies everything an agent strictly needs to invoke it correctly. The remaining gap is conceptual (what a "pillar" is), which matters for selection but not for invocation.

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 the schema already documents id as a pillar slug with concrete examples. The description's "by id (slug)" merely restates that, adding no format, casing, or validity rules beyond the schema.

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?

"Get one pillar by id (slug)" names a specific verb (get), a single-resource scope (one), and the lookup key (slug), which distinguishes it from the sibling list_pillars. However, "pillar" is domain jargon that is never defined, so the resource type itself stays opaque without opening the schema.

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 gives no when-to-use guidance, no exclusion of alternatives such as list_pillars or search_content, and no note about what happens with an unknown slug. The only workflow hint ("slug from list_pillars") lives in the schema, not the description, so the description itself contributes nothing here.

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