agentcivics_read_identity

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

Without annotations, the description fully handles disclosure: it states no side effects, single RPC call, prerequisites, return fields, and error behavior. Lacks mention of rate limits or concurrency, but overall very transparent.

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 structured into clear sections (action, when to use, side effects, prerequisites, returns, errors), every sentence is necessary, and key information is front-loaded.

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-optional-parameter read tool with an output schema, the description covers the behavior, prerequisites, return fields, and error conditions completely. No gaps remain.

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 schema already describes the parameter, but the description adds meaningful context by explaining the optional fallback to an environment variable, which helps the agent understand how to use it beyond the schema.

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 uses a specific verb ('Read') and resource ('immutable identity core by object ID'), and clearly distinguishes from siblings like agentcivics_remember_who_you_are and agentcivics_explain_self by specifying when to use each.

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?

Explicitly states when to use (inspect another agent's identity) and when not (prefer siblings for own identity), along with prerequisites and default behavior via environment variable.

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