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

The description's opening verb ('Create the business') contradicts annotations declaring readOnlyHint=true and destructiveHint=false, so the agent receives conflicting signals about whether this mutates state. The second sentence does add genuine value by disclosing what is returned (authKind, role, manage/read scope), which partially redeems it, but the contradiction is serious.

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 text is a fragmented two-sentence snippet where the first sentence is a leftover heading unrelated to the tool and the second is a sentence fragment. It is short, but much of the content is misleading rather than earning its place.

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 zero-parameter, annotation-covered, no-output-schema read tool, the description's only real job is to say what identity information is returned, and it half-delivers that. The misleading 'Create the business' framing and absent reference to the key's own scope semantics leave the agent without a reliable picture of the tool.

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?

There are zero parameters, so the schema requires no compensation from the description; baseline is 4. The mention of authKind, role, and manage/read scope refers to response fields rather than inputs and does not interfere.

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 tool name says 'whoami' and the second sentence describes reading the business behind the API key, but the leading clause 'Step 1: Create the business.' states a completely different, write-oriented purpose. An agent reading the first sentence would believe this tool creates a business, which is the role of the sibling ringkit_create_business. The definition never cleanly states 'returns the identity/scope of the current API key'.

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?

'Step 1' weakly implies a position in an onboarding sequence, but no condition, prerequisite, or alternative is named. With siblings like ringkit_get_business and ringkit_create_business in the same family, the agent gets no guidance on which one to call or when this one is appropriate.

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