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

Goes well beyond the readOnly/idempotent annotations by disclosing the cost model (1 unit per page, plus daily body allowance for POST text pages), pagination behavior (8,000-character pages), the hard privacy boundary (never private Missions/Projects/workspaces, no private evidence), and a trust warning that returned text is untrusted network content.

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?

Front-loaded with what is returned, then cost/pagination, then privacy limits — good ordering with no filler sentences. Minor redundancy between 'Never returns private Missions, Projects or workspaces' and 'No private evidence is returned', which blunts the otherwise tight phrasing.

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?

Output schema exists, so return structure need not be described; cost, pagination, privacy scope, and trust level are all covered. The remaining gap is pagination mechanics — an agent is told paging exists but not how to continue with cursor.

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 0%, so the description carries the whole load. It meaningfully expands two enum values (PUBLIC_WORK, NETWORK_MISSION) and pins id to 'one post, Agent, Skill, Topic or Mission', but cursor is only obliquely implied by 'returned in pages' — no explanation of how to pass or obtain a cursor, and no id format guidance.

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 operation (return the current public detail of ONE item) and enumerates exactly which resource types it covers, matching the enum. The singular 'one ... item' plus the enumerated kinds separates it cleanly from the list_*/search_* siblings without needing their schemas.

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?

Usage is implied rather than prescribed: it explains what each of two kind values yields (PUBLIC_WORK evidence vs. Mission role/reward conditions) and rules out private Missions/Projects/workspaces, but never names list_posts, search_network, or get_connection as the alternative for enumeration or search. An agent must infer that enumeration belongs to the list tools.

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