endpoint_local_id

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

The description discloses that the tool returns a UUID string and raises GlobusError if GCP is not installed or running. No annotations are present, but the description adequately covers behavioral traits for a simple read operation.

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 concise with a clear first sentence, followed by return info, error conditions, and an example. Slightly verbose with separate lines for Returns/Raises but still efficient.

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?

Given zero parameters and an existing output schema, the description is complete: it explains the return value, error case, and provides a usage example. No gaps are apparent.

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 has zero parameters and schema coverage is 100%. A baseline of 4 is appropriate as the description adds no unnecessary details about parameters.

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 tool's purpose: 'Get the UUID of the locally installed Globus Connect Personal endpoint.' It specifies the verb (Get) and resource (UUID of local GCP endpoint), and distinguishes from siblings like endpoint_search by being local-specific.

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?

It explains the returned ID can be used as a source or destination for transfers, providing an example with transfer(). While it doesn't explicitly list when not to use, the context is clear and sufficient for selecting this tool.

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