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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond that: it discloses that the response includes publication status, visitor-facing copy, limits, run frequency, and a drift signal ('whether the workflow or agent changed since the page was published'). It does not say what happens when the share_id is unknown or unpublished.

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?

The resource is front-loaded in the opening clause and the rest is a compact enumeration of returned fields, with no filler. It is a single long run-on sentence with a parenthetical detour about agent-specific copy, which slightly hurts scannability but every clause carries information.

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?

With no output schema, the description carries the burden of describing the response and does so thoroughly, covering URLs, status, visitor copy, inputs, limits, usage counts and drift. For a one-parameter read tool with full annotation coverage this is nearly sufficient; only error/failure behavior and the possible values of 'kind' are left out.

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% and the single parameter is already documented as coming from list_shares, share_workflow or share_agent. The description adds no further meaning about share_id, so the schema does all the work and the baseline of 3 applies.

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?

The description names the specific resource (one share page, either a workflow page or an agent page) and enumerates exactly what it yields, which clearly separates it from list_shares and the mutation siblings like update_share. It never states a verb such as 'retrieve', relying on the title 'Read a share page' for that, and it does not explicitly contrast itself with run_share or use_share.

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 or when-not-to-use guidance and no named alternative for fetching share data. The only usage signal is implicit: it returns a single page, so the id must come from a listing or share tool. The phrase 'see kind' points at a returned field, not a documented way to pick between the workflow and agent variants.

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