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

The description indicates a read operation returning details, which aligns with the readOnlyHint and idempotentHint annotations. It does not add much behavioral detail beyond the annotations, but there is no contradiction.

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 description is short but contains redundancy: the 'Guidance' line repeats the first sentence almost verbatim. The appended 'context' fragment feels bolted on and the overall structure is not clean.

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 simple read tool with no output schema, the description is reasonably complete in stating that it returns details for the identified media. However, it does not clarify what 'paragraph media' is or what the returned details contain, relying on context from sibling tools.

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?

All three parameters are covered by the schema with clear descriptions like 'Unique ID of the media' and similar. The tool description adds no extra semantic information beyond the schema, so it meets the baseline but does not exceed it.

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 clearly states the tool returns details of a paragraph media and identifies the key object. It is slightly generic and does not elaborate on what 'details' includes, but the core purpose is unambiguous.

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?

No guidance is provided on when to use this tool instead of the many sibling get/list tools. The 'Guidance' text merely repeats the description, and the appended context line does not offer decision guidance.

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