rlm_tenant_profile_get

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

Without annotations, the description reveals the optional nature of tenant_id and that the latest profile is returned when omitted. Lacks further detail on permissions or side effects but adds value beyond a generic 'get'.

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 sentences, no redundant text. Concise, but the contradiction reduces effectiveness.

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 simple getter with one optional parameter, the description covers basic functionality. However, the contradiction limits completeness; with consistent info it would be higher.

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 description contradicts the input schema: description says 'returns latest profile' when tenant_id is not specified, but schema description says 'returns all'. This conflict undermines clarity and adds no value.

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 'tenant profile(s)', and specifies the scope 'for a project'. It also distinguishes behavior when tenant_id is not specified.

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?

Implied usage is to retrieve tenant profiles. There is no explicit guidance on when not to use or alternatives, though the description is sufficient for basic selection.

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