gitea_get_organization

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic retrieval operation without mentioning safety (read-only status), authentication requirements, rate limits, or what specific organization information is returned.

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 a single efficient sentence. The '[UNIFIED]' prefix appears to be metadata noise rather than functional documentation, but the core statement is appropriately concise with no wasted words.

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?

Given zero schema coverage, missing annotations, and no output schema, the description is insufficient. It fails to document the 'site' parameter, describe return values, or explain what 'information' about the organization is actually retrieved.

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?

With 0% schema description coverage, the description partially compensates by implying the 'org' parameter is the organization name ('by name'). However, the 'site' parameter is completely undocumented in both schema and description, leaving critical context gaps for multi-instance Gitea setups.

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 verb (Get) and resource (Gitea organization) and specifies the lookup method (by name), which implicitly distinguishes it from the sibling gitea_list_organizations. However, it does not explicitly contrast with siblings or clarify that this retrieves a single organization versus a list.

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 provided on when to use this tool versus alternatives like gitea_list_organizations, nor any prerequisites (e.g., needing the exact organization name) or error conditions mentioned.

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