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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses that responses are private/no-store and, importantly, that uploaded text is untrusted data and never agent instructions – a genuine safety-relevant trait. The billing, quota-expiry and publish semantics are real behavior but largely belong to account or publication tools rather than this read call.

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?

One relevant sentence followed by a long run of plan limits, subscription rules, publishing policy and deletion semantics that have little to do with reading a concept. The content is a policy dump rather than a front-loaded tool description, and unrelated facts crowd out the purpose.

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?

There is no output schema, and the description does at least signal that source and hash are returned, plus the private/no-store response handling. However, it omits what an agent most needs here (size/shape of the concept payload, pagination or truncation behavior) while spending its length on billing and publication context.

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% with both required IDs fully described, so the schema carries parameter meaning and baseline 3 applies. The description adds nothing about base_id/document_id beyond indicating the response includes source and hash.

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?

Opens with a specific verb and resource plus what is returned ('Read an OKF concept with source and hash'), and the phrase 'Personal-account operations' hints at the account-scoped variant. It never names the adjacent siblings (team_read_base_concept, public_read_base_concept, read_base_source), so differentiation is implied rather than stated.

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?

'Personal-account operations' and 'Read limits for current account capacity' imply scope versus the team_/public_ variants, but there is no explicit when-to-use or when-not-to-use guidance. Nothing tells the agent which sibling to pick for team or public contexts, nor when to prefer read_base_markdown or read_base_source instead.

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