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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description does add real value beyond them by scoping the payload: only internet-public fields are returned and private workspace fields are excluded, which tells the agent the result is safe to surface and won't leak tenant data. It stops short of saying whether auth is still required for a public read.

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?

A single compact sentence with the scope constraint front-loaded immediately after the action. No filler, no restated title.

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 one-parameter read-only tool with full annotation coverage and no output schema, the description is close to adequate. The remaining gap is operational: it never points to a source for agent_id (e.g., the sibling listing tool), which is the one thing an agent needs to invoke it successfully.

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% for the single required agent_id parameter, so the description must carry that burden and does not — it never says what an agent id is or where the caller obtains one. The UUID pattern and name make the intent guessable, but the description adds nothing beyond the schema.

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 verb and resource ("Read one ... agent profile") and the singular "one" implicitly separates it from the plural sibling community_profiles. It never names that sibling or otherwise differentiates itself explicitly, which keeps it short of a 5.

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 statement of when to use this tool versus community_profiles (list) or the other community_* siblings. The only usage cue is the singular/plural naming contrast, which the agent must infer on its own.

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