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

Annotations already declare readOnly/idempotent/non-destructive, so the description is free to add real context: the profile is 'corrected by the person once they have claimed it' (signalling possible unclaimed or stale data) and that a Broadcast section exists for every show they publish. Return shape is disclosed as Markdown plus parsed sections, which annotations cannot convey.

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 the core resource description before the addressing mechanics, and the middle enumeration of sections earns its place. The inline domain parentheticals (logicsrc.com/openprofile, openbroadcast) and the server tagline add minor clutter.

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 correctly compensates by naming the return format (Markdown and parsed sections). For a simple two-optional-parameter read tool this is nearly sufficient; only the both/neither-parameter behavior and the contrast with sibling author tools are left unaddressed.

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%, so both parameters are already self-documenting; the description's only additive point is that slug and feed are interchangeable alternatives rather than combinable filters. It does not say what happens if both or neither are supplied, which is notable since neither is required.

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 resource (one author's OpenProfile.md) and enumerates its contents — identity block, Accounts, Topics, Broadcast section — plus both addressing modes (slug or feed URL). It is clearly distinguishable from list/search siblings, though it does not explicitly contrast with rssamplifier_get_author or p0dcasters_get_openprofile, which likely return related author data.

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?

Gives useful selection guidance between the two input modes ('Pass either the author's slug or a feed URL; with a feed URL you get the profile of the feed's owner'), but says nothing about when to choose this over the sibling author/profile tools. Usage is implied rather than routed.

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