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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds a genuinely useful behavioral detail not present elsewhere: a cost of 15 credits per call. It does not describe rate limits, pagination, or failure modes, so it is above baseline but not rich.

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?

Two lean sentences, purpose front-loaded, cost appended on its own line. Nothing is redundant, though the profile-field enumeration slightly overlaps what a schema/output could convey.

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 tool with annotations covering safety, the description is nearly sufficient, and enumerating the returned fields partially compensates for the absent output schema. It lacks any note on invalid community_id handling or pagination, but little else is missing.

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% and the single parameter (community_id) is never mentioned in the description, so no meaning is added. The parameter name is largely self-explanatory for a single simple read, which keeps this at a middling score rather than poor.

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 (Return) and resource (a Community's profile) and even enumerates the returned fields (name, purpose, rules, member count, moderators). The purpose is unmistakable, but it does not distinguish itself from community-related siblings like community_tweets or list_members.

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 when-to-use, when-not-to-use, or alternative routing guidance. The sibling list contains several community/user tools (list_members, community_tweets, user_info) an agent would have to disambiguate by inference alone.

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