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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing beyond the resource name. It does not say whether this is a read-only lookup, whether it requires any authorization, or what form the response takes.

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 short sentence with no waste, appropriately sized for a zero-argument getter. It is a fragment rather than a well-formed description, which keeps it just below the top.

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?

With no annotations and no output schema, the description is the only source of information about what the 'basic administrative profile' contains, and it gives no detail on the fields or shape of the result. For a tool whose entire contract is the returned data, this leaves the agent guessing.

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 is trivially complete and there is no parameter semantics for the description to add. Baseline 4 applies for a no-argument tool.

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 names the resource — an 'administrative profile of a territory' — which clarifies the domain beyond the bare name get_basic_profile, and the sibling names (get_identity, get_territory_hierarchy) suggest it is the territory-level variant. However, it is a noun phrase with no verb, and it never distinguishes itself from get_identity or get_territory_hierarchy, both of which also sound like territory lookups.

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?

There is no guidance on when to call this versus get_identity, get_sources, or get_territory_hierarchy, and no stated prerequisites. The agent must infer the selection criteria entirely from the name.

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