Get tribe

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

The description richly supplements the readOnlyHint annotation by disclosing actual behavioral details: private tribes return 404 to unauthorized users, the shareUrl appears only for owned private tribes, it is view-only, and rotating it revokes old links. These are important, non-obvious behaviors an agent needs to know.

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 front-loaded with the core response contents and then adds exclusion, visibility, and shareUrl details. Every sentence contributes essential behavioral information, and nothing is redundant or wasted.

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 single-parameter read-only tool with no output schema, the description is exceptionally complete: it lists response fields, states what is excluded, clarifies access control and 404 semantics, explains the shareUrl feature, and mentions how to revoke links. No critical information 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?

The input schema already fully documents the single parameter, including the UUID format and the note that it must be the uuid field, not slug or numeric id. The description does not add additional parameter-specific semantics, so the baseline score of 3 for 100% schema coverage 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?

Description clearly states the operation ('Get a tribe') and the exact resource fields returned: name, description, visibility, owner, tags and timestamps. It also explicitly distinguishes itself from tribeunal_list_tribe_members by noting the member roster is not included, which helps an agent differentiate from a closely related sibling tool.

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?

Provides explicit guidance on when to use this tool versus tribeunal_list_tribe_members for the roster, and details visibility rules for private tribes including the 404 behavior and who can read. This goes beyond generic usage and clearly routes the agent to the right alternative.

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