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

With no annotations, the description carries the full burden; it does disclose one genuinely useful behavioral constraint — that parallel upload from MCP is not supported — which is exactly the kind of context an agent could not get from schema. However, it doesn't say whether the tool is read-only (implicit from 'requirements' but unstated) or what it returns.

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 compact sentence, front-loaded with the primary resource (media limits) and followed by the constraint. It's short to the point of being cryptic — the telegraphic phrasing and missing verb cost it a point — but there is no filler.

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 no-parameter, no-output-schema informational tool, the description should convey roughly what information comes back. 'Media limits and the supported way to attach photos' hints at the content but doesn't specify the shape (sizes, formats, counts) or whether it must be re-checked per session.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 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 a specific resource (media limits) and a specific bit of knowledge (the supported way to attach photos), so the agent knows this is an informational lookup rather than an action. It's distinct from the sibling tools (memories, places, connection status), though the verb is implicit and the phrasing is somewhat telegraphic.

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?

The parenthetical '(no parallel upload from MCP)' implies this should be consulted before attempting to attach photos, but it never states explicitly when to call it or what to do with the result. The usage context is inferable rather than stated.

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