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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered and the description does not contradict it. The description adds the return-field summary (name, domain, settings summary) plus the underlying GET /organization endpoint, which is useful for a tool without an output schema, but it says nothing about auth requirements, rate limits, or scoping.

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 front-loaded sentence plus the endpoint reference; every element earns its place and nothing is padded. The resource is stated before the parenthetical details.

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 singleton getter with annotations covering read-only safety, the description supplies the resource identity and a summary of returned fields, which is what an agent needs since there is no output schema. Only minor gaps remain (unknown whether the response is scoped by API key/tenant, no auth note).

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 the schema carries no parameter semantics to document and the baseline of 4 applies. Nothing in the description misleads about inputs, and there are no fields an agent could get wrong.

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 (get) and resource (the current Kisi organization), and parenthetically names the kind of data returned (name, domain, settings summary). It is distinguishable from siblings like kisi_get_current_user or kisi_get_group by resource, though it never explicitly contrasts itself with them.

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?

Usage is implied rather than stated: it is the singleton-organization getter with no parameters, so an agent can infer it is the general-purpose org lookup. There is no explicit when-to-use guidance, no prerequisite/concurrency notes, and no named alternative (e.g. vs. kisi_get_current_user).

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